Uplink signal control

ABSTRACT

A base station may cancel or delay (e.g., pre-empt) a transmission from a wireless device by sending a pre-emption indication to the wireless device. Based on receiving the pre-emption indication, the wireless device may cancel the transmission, store an indication associated with the cancelled transmission, and/or store the cancelled transmission in a data buffer. The base station may request transmission of the data unit (e.g., at a later time) by transmitting another indication.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/785,100 filed on Feb. 7, 2020, which claims the benefit of U.S.Provisional Application No. 62/802,450, titled “Uplink Pre-emptionMechanism” and filed on Feb. 7, 2019. Each of the above-referencedapplications is hereby incorporated by reference in its entirety.

BACKGROUND

A base station sends a message, indicating an uplink grant, to awireless device. The wireless device uses an uplink grant to send amessage to the base station.

SUMMARY

The following summary presents a simplified summary of certain features.The summary is not an extensive overview and is not intended to identifykey or critical elements.

Systems, methods, and apparatuses for wireless communications aredescribed. Transmissions from a wireless device may be cancelled/delayedto enable the wireless device to send another transmission (e.g., formore urgent communications, higher priority service, etc.). A basestation may send an indication (e.g., a pre-emption indication) to thewireless device indicating that the wireless device is to pre-empt(e.g., cancel and/or delay) a transmission (e.g., a scheduledtransmission based on an uplink grant). Cancelling the pre-emptedtransmission may result in misalignment between the wireless device andthe base station, wherein the base station may not know whether thewireless device may operate as if the cancelled transmission has beensent to the base station, not sent to the base station, and/or sent/notsent based on one or more criteria. Based on receiving the pre-emptionindication, the wireless device may reduce the likelihood of suchmisalignment, for example, by cancelling the pre-empted transmission,storing an indication associated with the pre-empted transmission,and/or storing information (e.g., data, message, scheduled transmission,etc.) associated with the pre-empted transmission. The examplesdescribed herein may result in advantages such as enabling higher uplinkthroughput, higher energy efficiency, and/or reduced transmissionlatency (e.g., for transmission of a pre-empted transmission at thelater time).

These and other features and advantages are described in greater detailbelow.

BRIEF DESCRIPTION OF THE DRAWINGS

Some features are shown by way of example, and not by limitation, in theaccompanying drawings. In the drawings, like numerals reference similarelements.

FIG. 1 shows an example radio access network (RAN) architecture.

FIG. 2A shows an example user plane protocol stack.

FIG. 2B shows an example control plane protocol stack.

FIG. 3 shows an example wireless device and two base stations.

FIG. 4A, FIG. 4B, FIG. 4C, and FIG. 4D show examples of uplink anddownlink signal transmission.

FIG. 5A shows an example uplink channel mapping and example uplinkphysical signals.

FIG. 5B shows an example downlink channel mapping and example downlinkphysical signals.

FIG. 6 shows an example transmission time and/or reception time for acarrier.

FIG. 7A and FIG. 7B show example sets of orthogonal frequency divisionmultiplexing (OFDM) subcarriers.

FIG. 8 shows example OFDM radio resources.

FIG. 9A shows an example channel state information reference signal(CSI-RS) and/or synchronization signal (SS) block transmission in amulti-beam system.

FIG. 9B shows an example downlink beam management procedure.

FIG. 10 shows an example of configured bandwidth parts (BWPs).

FIG. 11A and FIG. 11B show examples of multi connectivity.

FIG. 12 shows an example of a random access procedure.

FIG. 13 shows example medium access control (MAC) entities.

FIG. 14 shows an example RAN architecture.

FIG. 15 shows example radio resource control (RRC) states.

FIG. 16A, FIG. 16B and FIG. 16C show example MAC subheaders formats.

FIG. 17A and FIG. 17B show examples MAC data unit formats.

FIG. 18 shows example logical channel identifier (LCID) values.

FIG. 19 shows example LCID values.

FIG. 20A and FIG. 20B show example secondary cell (SCell)activation/deactivation MAC control element (CE) formats.

FIG. 21A shows an example of an SCell hibernation MAC CE format.

FIG. 21B shows an example of an SCell hibernation MAC CE format.

FIG. 21C shows example MAC CEs for SCell state transitions.

FIG. 22 shows example downlink control information (DCI) formats.

FIG. 23 shows example BWP management on an SCell.

FIG. 24 shows an example DRX operation.

FIG. 25 shows an example DRX operation.

FIG. 26 shows an example hybrid automatic repeat request (HARQ)operation.

FIG. 27 shows an example HARQ operation.

FIG. 28 shows an example for uplink pre-emption.

FIG. 29 shows an example for uplink pre-emption.

FIG. 30 shows an example for uplink pre-emption.

FIG. 31 shows an example of an enhanced HARQ operation.

FIG. 32 shows an example of an enhanced HARQ operation.

FIG. 33 shows an example of an enhanced HARQ operation.

FIG. 34 shows an example of an enhanced HARQ operation.

FIG. 35 shows example BWP state management.

FIG. 36 shows example BWP state management.

FIG. 37 shows an example DRX operation.

FIG. 38 shows an example method for an enhanced HARQ operation.

FIG. 39 shows example elements of a computing device that may be used toimplement any of the various devices described herein.

DETAILED DESCRIPTION

The accompanying drawings and descriptions provide examples. It is to beunderstood that the examples shown in the drawings and/or described arenon-exclusive and that there are other examples of how features shownand described may be practiced.

Examples are provided for operation of wireless communication systemswhich may be used in the technical field of multicarrier communicationsystems. More particularly, the technology described herein may relateto prioritization of transmissions in wireless communications.

The following acronyms are used throughout the drawings and/ordescriptions, and are provided below for convenience although otheracronyms may be introduced in the detailed description:

3GPP 3rd Generation Partnership Project

5GC 5G Core Network

ACK Acknowledgement

AMF Access and Mobility Management Function

ARQ Automatic Repeat Request

AS Access Stratum

ASIC Application-Specific Integrated Circuit

BA Bandwidth Adaptation

BCCH Broadcast Control Channel

BCH Broadcast Channel

BPSK Binary Phase Shift Keying

BWP Bandwidth Part

CA Carrier Aggregation

CC Component Carrier

CCCH Common Control CHannel

CDMA Code Division Multiple Access

CE Control Element

CN Core Network

CORESET Control Resource Set

CP Cyclic Prefix

CP-OFDM Cyclic Prefix-Orthogonal Frequency Division Multiplex

C-RNTI Cell-Radio Network Temporary Identifier

CS Configured Scheduling

CSI Channel State Information

CSI-RS Channel State Information-Reference Signal

CQI Channel Quality Indicator

CRI CSI-RS resource indicator

CSS Common Search Space

CU Central Unit

DC Dual Connectivity

DCCH Dedicated Control Channel

DCI Downlink Control Information

DL Downlink

DL-SCH Downlink Shared CHannel

DM-RS DeModulation Reference Signal

DRB Data Radio Bearer

DRX Discontinuous Reception

DTCH Dedicated Traffic Channel

DU Distributed Unit

EPC Evolved Packet Core

E-UTRA Evolved UMTS Terrestrial Radio Access

E-UTRAN Evolved-Universal Terrestrial Radio Access Network

FDD Frequency Division Duplex

FPGA Field Programmable Gate Arrays

F1-C F1-Control plane

F1-U F1-User plane

gNB next generation Node B

HARQ Hybrid Automatic Repeat reQuest

HDL Hardware Description Languages

IE Information Element

IP Internet Protocol

LCID Logical Channel Identifier

LI Layer Indicator

LTE Long Term Evolution

MAC Medium Access Control

MCG Master Cell Group

MCS Modulation and Coding Scheme

MeNB Master evolved Node B

MIB Master Information Block

MME Mobility Management Entity

MN Master Node j

NACK Negative Acknowledgement

NAS Non-Access Stratum

NDI New Data Indicator

NG CP Next Generation Control Plane

NGC Next Generation Core

NG-C NG-Control plane

ng-eNB next generation evolved Node B

NG-U NG-User plane

NR New Radio

NR MAC New Radio MAC

NR PDCP New Radio PDCP

NR PHY New Radio PHYsical

NR RLC New Radio RLC

NR RRC New Radio RRC

NSSAI Network Slice Selection Assistance Information

O&M Operation and Maintenance

OFDM Orthogonal Frequency Division Multiplexing

PBCH Physical Broadcast CHannel

PCC Primary Component Carrier

PCCH Paging Control CHannel

PCell Primary Cell

PCH Paging CHannel

PDCCH Physical Downlink Control CHannel

PDCP Packet Data Convergence Protocol

PDSCH Physical Downlink Shared CHannel

PDU Protocol Data Unit

PHICH Physical HARQ Indicator CHannel

PHY PHYsical

PLMN Public Land Mobile Network

PMI Precoding Matrix Indicator

PRACH Physical Random Access CHannel

PRB Physical Resource Block

PSCell Primary Secondary Cell

PSS Primary Synchronization Signal

pTAG primary Timing Advance Group

PT-RS Phase Tracking Reference Signal

PUCCH Physical Uplink Control CHannel

PUSCH Physical Uplink Shared CHannel

QAM Quadrature Amplitude Modulation

QCLed Quasi-Co-Located

QCL Quasi-Co-Location

QFI Quality of Service Indicator

QoS Quality of Service

QPSK Quadrature Phase Shift Keying

RA Random Access

RACH Random Access CHannel

RAN Radio Access Network

RAT Radio Access Technology

RA-RNTI Random Access-Radio Network Temporary Identifier

RB Resource Blocks

RBG Resource Block Groups

RI Rank indicator

RLC Radio Link Control

RLM Radio Link Monitoring

RNTI Radio Network Temporary Identifier

RRC Radio Resource Control

RRM Radio Resource Management

RS Reference Signal

RV Redundancy Version

RSRP Reference Signal Received Power

SCC Secondary Component Carrier

SCell Secondary Cell

SCG Secondary Cell Group

SC-FDMA Single Carrier-Frequency Division Multiple Access

SDAP Service Data Adaptation Protocol

SDU Service Data Unit

SeNB Secondary evolved Node B

SFN System Frame Number

S-GW Serving GateWay

SI System Information

SIB System Information Block

SINR Signal-to-Interference-plus-Noise Ratio

SMF Session Management Function

SN Secondary Node

SpCell Special Cell

SRB Signaling Radio Bearer

SRS Sounding Reference Signal

SS Synchronization Signal

SSB Synchronization Signal Block

SSBRI Synchronization Signal Block Resource Indicator

SSS Secondary Synchronization Signal

sTAG secondary Timing Advance Group

TA Timing Advance

TAG Timing Advance Group

TAI Tracking Area Identifier

TAT Time Alignment Timer

TB Transport Block

TC-RNTI Temporary Cell-Radio Network Temporary Identifier

TCI Transmission Configuration Indication

TDD Time Division Duplex

TDMA Time Division Multiple Access

TRP Transmission Reception Point

TTI Transmission Time Interval

UCI Uplink Control Information

UE User Equipment

UL Uplink

UL-SCH Uplink Shared CHannel

UPF User Plane Function

UPGW User Plane Gateway

URLLC Ultra-Reliable Low-Latency Communication

V2X Vehicle-to-everything

VHDL VHSIC Hardware Description Language

Xn-C Xn-Control plane

Xn-U Xn-User plane

Examples described herein may be implemented using various physicallayer modulation and transmission mechanisms. Example transmissionmechanisms may include, but are not limited to: Code Division MultipleAccess (CDMA), Orthogonal Frequency Division Multiple Access (OFDMA),Time Division Multiple Access (TDMA), Wavelet technologies, and/or thelike. Hybrid transmission mechanisms such as TDMA/CDMA, and/or OFDM/CDMAmay be used. Various modulation schemes may be used for signaltransmission in the physical layer. Examples of modulation schemesinclude, but are not limited to: phase, amplitude, code, a combinationof these, and/or the like. An example radio transmission method mayimplement Quadrature Amplitude Modulation (QAM) using Binary Phase ShiftKeying (BPSK), Quadrature Phase Shift Keying (QPSK), 16-QAM, 64-QAM,256-QAM, 1024-QAM and/or the like. Physical radio transmission may beenhanced by dynamically or semi-dynamically changing the modulation andcoding scheme, for example, depending on transmission requirementsand/or radio conditions.

FIG. 1 shows an example Radio Access Network (RAN) architecture. A RANnode may comprise a next generation Node B (gNB) (e.g., 120A, 120B)providing New Radio (NR) user plane and control plane protocolterminations towards a first wireless device (e.g., 110A). A RAN nodemay comprise a base station such as a next generation evolved Node B(ng-eNB) (e.g., 120C, 120D), providing Evolved UMTS Terrestrial RadioAccess (E-UTRA) user plane and control plane protocol terminationstowards a second wireless device (e.g., 110B). A first wireless device110A may communicate with a base station, such as a gNB 120A, over a Uuinterface. A second wireless device 110B may communicate with a basestation, such as an ng-eNB 120D, over a Uu interface. The wirelessdevices 110A and/or 110B may be structurally similar to wireless devicesshown in and/or described in connection with other drawing figures. TheNode B 120A, the Node B 120B, the Node B 120C, and/or the Node B 120Dmay be structurally similar to Nodes B and/or base stations shown inand/or described in connection with other drawing figures.

A base station, such as a gNB (e.g., 120A, 120B, etc.) and/or an ng-eNB(e.g., 120C, 120D, etc.) may host functions such as radio resourcemanagement and scheduling, IP header compression, encryption andintegrity protection of data, selection of Access and MobilityManagement Function (AMF) at wireless device (e.g., User Equipment (UE))attachment, routing of user plane and control plane data, connectionsetup and release, scheduling and transmission of paging messages (e.g.,originated from the AMF), scheduling and transmission of systembroadcast information (e.g., originated from the AMF or Operation andMaintenance (O&M)), measurement and measurement reporting configuration,transport level packet marking in the uplink, session management,support of network slicing, Quality of Service (QoS) flow management andmapping to data radio bearers, support of wireless devices in aninactive state (e.g., RRC_INACTIVE state), distribution function forNon-Access Stratum (NAS) messages, RAN sharing, dual connectivity,and/or tight interworking between NR and E-UTRA.

One or more first base stations (e.g., gNBs 120A and 120B) and/or one ormore second base stations (e.g., ng-eNBs 120C and 120D) may beinterconnected with each other via Xn interface. A first base station(e.g., gNB 120A, 120B, etc.) or a second base station (e.g., ng-eNB120C, 120D, etc.) may be connected via NG interfaces to a network, suchas a 5G Core Network (5GC). A 5GC may comprise one or more AMF/User PlanFunction (UPF) functions (e.g., 130A and/or 130B). A base station (e.g.,a gNB and/or an ng-eNB) may be connected to a UPF via an NG-User plane(NG-U) interface. The NG-U interface may provide delivery (e.g.,non-guaranteed delivery) of user plane Protocol Data Units (PDUs)between a RAN node and the UPF. A base station (e.g., a gNB and/or anng-eNB) may be connected to an AMF via an NG-Control plane (NG-C)interface. The NG-C interface may provide functions such as NG interfacemanagement, wireless device (e.g., UE) context management, wirelessdevice (e.g., UE) mobility management, transport of NAS messages,paging, PDU session management, configuration transfer, and/or warningmessage transmission.

A UPF may host functions such as anchor point for intra-/inter-RadioAccess Technology (RAT) mobility (e.g., if applicable), external PDUsession point of interconnect to data network, packet routing andforwarding, packet inspection and user plane part of policy ruleenforcement, traffic usage reporting, uplink classifier to supportrouting traffic flows to a data network, branching point to supportmulti-homed PDU session, quality of service (QoS) handling for userplane, packet filtering, gating, Uplink (UL)/Downlink (DL) rateenforcement, uplink traffic verification (e.g., Service Data Flow (SDF)to QoS flow mapping), downlink packet buffering, and/or downlink datanotification triggering.

An AMF may host functions such as NAS signaling termination, NASsignaling security, Access Stratum (AS) security control, inter CoreNetwork (CN) node signaling (e.g., for mobility between 3rd GenerationPartnership Project (3GPP) access networks), idle mode wireless devicereachability (e.g., control and execution of paging retransmission),registration area management, support of intra-system and inter-systemmobility, access authentication, access authorization including check ofroaming rights, mobility management control (e.g., subscription and/orpolicies), support of network slicing, and/or Session ManagementFunction (SMF) selection.

FIG. 2A shows an example user plane protocol stack. A Service DataAdaptation Protocol (SDAP) (e.g., 211 and 221), Packet Data ConvergenceProtocol (PDCP) (e.g., 212 and 222), Radio Link Control (RLC) (e.g., 213and 223), and Medium Access Control (MAC) (e.g., 214 and 224) sublayers,and a Physical (PHY) (e.g., 215 and 225) layer, may be terminated in awireless device (e.g., 110) and in a base station (e.g., 120) on anetwork side. A PHY layer may provide transport services to higherlayers (e.g., MAC, RRC, etc.). Services and/or functions of a MACsublayer may comprise mapping between logical channels and transportchannels, multiplexing and/or demultiplexing of MAC Service Data Units(SDUs) belonging to the same or different logical channels into and/orfrom Transport Blocks (TBs) delivered to and/or from the PHY layer,scheduling information reporting, error correction through HybridAutomatic Repeat request (HARQ) (e.g., one HARQ entity per carrier forCarrier Aggregation (CA)), priority handling between wireless devicessuch as by using dynamic scheduling, priority handling between logicalchannels of a wireless device such as by using logical channelprioritization, and/or padding. A MAC entity may support one or multiplenumerologies and/or transmission timings. Mapping restrictions in alogical channel prioritization may control which numerology and/ortransmission timing a logical channel may use. An RLC sublayer maysupport transparent mode (TM), unacknowledged mode (UM), and/oracknowledged mode (AM) transmission modes. The RLC configuration may beper logical channel with no dependency on numerologies and/orTransmission Time Interval (TTI) durations. Automatic Repeat Request(ARQ) may operate on any of the numerologies and/or TTI durations withwhich the logical channel is configured. Services and functions of thePDCP layer for the user plane may comprise, for example, sequencenumbering, header compression and decompression, transfer of user data,reordering and duplicate detection, PDCP PDU routing (e.g., such as forsplit bearers), retransmission of PDCP SDUs, ciphering, deciphering andintegrity protection, PDCP SDU discard, PDCP re-establishment and datarecovery for RLC AM, and/or duplication of PDCP PDUs. Services and/orfunctions of SDAP may comprise, for example, mapping between a QoS flowand a data radio bearer. Services and/or functions of SDAP may comprisemapping a Quality of Service Indicator (QFI) in DL and UL packets. Aprotocol entity of SDAP may be configured for an individual PDU session.

FIG. 2B shows an example control plane protocol stack. A PDCP (e.g., 233and 242), RLC (e.g., 234 and 243), and MAC (e.g., 235 and 244)sublayers, and a PHY (e.g., 236 and 245) layer, may be terminated in awireless device (e.g., 110), and in a base station (e.g., 120) on anetwork side, and perform service and/or functions described above. RRC(e.g., 232 and 241) may be terminated in a wireless device and a basestation on a network side. Services and/or functions of RRC may comprisebroadcast of system information related to AS and/or NAS; paging (e.g.,initiated by a 5GC or a RAN); establishment, maintenance, and/or releaseof an RRC connection between the wireless device and RAN; securityfunctions such as key management, establishment, configuration,maintenance, and/or release of Signaling Radio Bearers (SRBs) and DataRadio Bearers (DRBs); mobility functions; QoS management functions;wireless device measurement reporting and control of the reporting;detection of and recovery from radio link failure; and/or NAS messagetransfer to/from NAS from/to a wireless device. NAS control protocol(e.g., 231 and 251) may be terminated in the wireless device and AMF(e.g., 130) on a network side. NAS control protocol may performfunctions such as authentication, mobility management between a wirelessdevice and an AMF (e.g., for 3GPP access and non-3GPP access), and/orsession management between a wireless device and an SMF (e.g., for 3GPPaccess and non-3GPP access).

A base station may configure a plurality of logical channels for awireless device. A logical channel of the plurality of logical channelsmay correspond to a radio bearer. The radio bearer may be associatedwith a QoS requirement. A base station may configure a logical channelto be mapped to one or more TTIs and/or numerologies in a plurality ofTTIs and/or numerologies. The wireless device may receive DownlinkControl Information (DCI) via a Physical Downlink Control CHannel(PDCCH) indicating an uplink grant. The uplink grant may be for a firstTTI and/or a first numerology and may indicate uplink resources fortransmission of a transport block. The base station may configure eachlogical channel in the plurality of logical channels with one or moreparameters to be used by a logical channel prioritization procedure atthe MAC layer of the wireless device. The one or more parameters maycomprise, for example, priority, prioritized bit rate, etc. A logicalchannel in the plurality of logical channels may correspond to one ormore buffers comprising data associated with the logical channel. Thelogical channel prioritization procedure may allocate the uplinkresources to one or more first logical channels in the plurality oflogical channels and/or to one or more MAC Control Elements (CEs). Theone or more first logical channels may be mapped to the first TTI and/orthe first numerology. The MAC layer at the wireless device may multiplexone or more MAC CEs and/or one or more MAC SDUs (e.g., logical channel)in a MAC PDU (e.g., transport block). The MAC PDU may comprise a MACheader comprising a plurality of MAC sub-headers. A MAC sub-header inthe plurality of MAC sub-headers may correspond to a MAC CE or a MAC SUD(e.g., logical channel) in the one or more MAC CEs and/or in the one ormore MAC SDUs. A MAC CE and/or a logical channel may be configured witha Logical Channel IDentifier (LCID). An LCID for a logical channeland/or a MAC CE may be fixed and/or pre-configured. An LCID for alogical channel and/or MAC CE may be configured for the wireless deviceby the base station. The MAC sub-header corresponding to a MAC CE and/ora MAC SDU may comprise an LCID associated with the MAC CE and/or the MACSDU.

A base station may activate, deactivate, and/or impact one or moreprocesses (e.g., set values of one or more parameters of the one or moreprocesses or start and/or stop one or more timers of the one or moreprocesses) at the wireless device, for example, by using one or more MACcommands. The one or more MAC commands may comprise one or more MACcontrol elements. The one or more processes may comprise activationand/or deactivation of PDCP packet duplication for one or more radiobearers. The base station may send (e.g., transmit) a MAC CE comprisingone or more fields. The values of the fields may indicate activationand/or deactivation of PDCP duplication for the one or more radiobearers. The one or more processes may comprise Channel StateInformation (CSI) transmission of on one or more cells. The base stationmay send (e.g., transmit) one or more MAC CEs indicating activationand/or deactivation of the CSI transmission on the one or more cells.The one or more processes may comprise activation and/or deactivation ofone or more secondary cells. The base station may send (e.g., transmit)a MAC CE indicating activation and/or deactivation of one or moresecondary cells. The base station may send (e.g., transmit) one or moreMAC CEs indicating starting and/or stopping of one or more DiscontinuousReception (DRX) timers at the wireless device. The base station may send(e.g., transmit) one or more MAC CEs indicating one or more timingadvance values for one or more Timing Advance Groups (TAGs).

FIG. 3 shows an example of base stations (base station 1, 120A, and basestation 2, 120B) and a wireless device 110. The wireless device 110 maycomprise a UE or any other wireless device. The base station (e.g.,120A, 120B) may comprise a Node B, eNB, gNB, ng-eNB, one or moretransmission and reception points, or any other base station. A wirelessdevice and/or a base station may perform one or more functions of arelay node. The base station 1, 120A, may comprise at least onecommunication interface 320A (e.g., a wireless modem, an antenna, awired modem, and/or the like), at least one processor 321A, and at leastone set of program code instructions 323A that may be stored innon-transitory memory 322A and executable by the at least one processor321A. The base station 2, 120B, may comprise at least one communicationinterface 320B, at least one processor 321B, and at least one set ofprogram code instructions 323B that may be stored in non-transitorymemory 322B and executable by the at least one processor 321B.

A base station may comprise any number of sectors, for example: 1, 2, 3,4, or 6 sectors. A base station may comprise any number of cells, forexample, ranging from 1 to 50 cells or more. A cell may be categorized,for example, as a primary cell or secondary cell. At Radio ResourceControl (RRC) connection establishment, re-establishment, handover,etc., a serving cell may provide NAS (non-access stratum) mobilityinformation (e.g., Tracking Area Identifier (TAI)). At RRC connectionre-establishment and/or handover, a serving cell may provide securityinput. This serving cell may be referred to as the Primary Cell (PCell).In the downlink, a carrier corresponding to the PCell may be a DLPrimary Component Carrier (PCC). In the uplink, a carrier may be an ULPCC. Secondary Cells (SCells) may be configured to form together with aPCell a set of serving cells, for example, depending on wireless devicecapabilities. In a downlink, a carrier corresponding to an SCell may bea downlink secondary component carrier (DL SCC). In an uplink, a carriermay be an uplink secondary component carrier (UL SCC). An SCell may ormay not have an uplink carrier.

A cell, comprising a downlink carrier and optionally an uplink carrier,may be assigned a physical cell ID and/or a cell index. A carrier(downlink and/or uplink) may belong to one cell. The cell ID and/or cellindex may identify the downlink carrier and/or uplink carrier of thecell (e.g., depending on the context it is used). A cell ID may beequally referred to as a carrier ID, and a cell index may be referred toas a carrier index. A physical cell ID and/or a cell index may beassigned to a cell. A cell ID may be determined using a synchronizationsignal transmitted via a downlink carrier. A cell index may bedetermined using RRC messages. A first physical cell ID for a firstdownlink carrier may indicate that the first physical cell ID is for acell comprising the first downlink carrier. The same concept may beused, for example, with carrier activation and/or deactivation (e.g.,secondary cell activation and/or deactivation). A first carrier that isactivated may indicate that a cell comprising the first carrier isactivated.

A base station may send (e.g., transmit) to a wireless device one ormore messages (e.g., RRC messages) comprising a plurality ofconfiguration parameters for one or more cells. One or more cells maycomprise at least one primary cell and at least one secondary cell. AnRRC message may be broadcasted and/or unicasted to the wireless device.Configuration parameters may comprise common parameters and dedicatedparameters.

Services and/or functions of an RRC sublayer may comprise at least oneof: broadcast of system information related to AS and/or NAS; paginginitiated by a 5GC and/or an NG-RAN; establishment, maintenance, and/orrelease of an RRC connection between a wireless device and an NG-RAN,which may comprise at least one of addition, modification, and/orrelease of carrier aggregation; and/or addition, modification, and/orrelease of dual connectivity in NR or between E-UTRA and NR. Servicesand/or functions of an RRC sublayer may comprise at least one ofsecurity functions comprising key management; establishment,configuration, maintenance, and/or release of Signaling Radio Bearers(SRBs) and/or Data Radio Bearers (DRBs); mobility functions which maycomprise at least one of a handover (e.g., intra NR mobility orinter-RAT mobility) and/or a context transfer; and/or a wireless devicecell selection and/or reselection and/or control of cell selection andreselection. Services and/or functions of an RRC sublayer may compriseat least one of QoS management functions; a wireless device measurementconfiguration/reporting; detection of and/or recovery from radio linkfailure; and/or NAS message transfer to and/or from a core networkentity (e.g., AMF, Mobility Management Entity (MME)) from and/or to thewireless device.

An RRC sublayer may support an RRC_Idle state, an RRC_Inactive state,and/or an RRC_Connected state for a wireless device. In an RRC_Idlestate, a wireless device may perform at least one of: Public Land MobileNetwork (PLMN) selection; receiving broadcasted system information; cellselection and/or re-selection; monitoring and/or receiving a paging formobile terminated data initiated by 5GC; paging for mobile terminateddata area managed by 5GC; and/or DRX for CN paging configured via NAS.In an RRC_Inactive state, a wireless device may perform at least one of:receiving broadcasted system information; cell selection and/orre-selection; monitoring and/or receiving a RAN and/or CN paginginitiated by an NG-RAN and/or a 5GC; RAN-based notification area (RNA)managed by an NG-RAN; and/or DRX for a RAN and/or CN paging configuredby NG-RAN/NAS. In an RRC_Idle state of a wireless device, a base station(e.g., NG-RAN) may keep a 5GC-NG-RAN connection (e.g., both C/U-planes)for the wireless device; and/or store a wireless device AS context forthe wireless device. In an RRC_Connected state of a wireless device, abase station (e.g., NG-RAN) may perform at least one of: establishmentof 5GC-NG-RAN connection (both C/U-planes) for the wireless device;storing a UE AS context for the wireless device; send (e.g., transmit)and/or receive of unicast data to and/or from the wireless device;and/or network-controlled mobility based on measurement results receivedfrom the wireless device. In an RRC_Connected state of a wirelessdevice, an NG-RAN may know a cell to which the wireless device belongs.

System information (SI) may be divided into minimum SI and other SI. Theminimum SI may be periodically broadcast. The minimum SI may comprisebasic information required for initial access and/or information foracquiring any other SI broadcast periodically and/or provisionedon-demand (e.g., scheduling information). The other SI may either bebroadcast, and/or be provisioned in a dedicated manner, such as eithertriggered by a network and/or upon request from a wireless device. Aminimum SI may be transmitted via two different downlink channels usingdifferent messages (e.g., MasterInformationBlock andSystemInformationBlockType1). Another SI may be transmitted viaSystemInformationBlockType2. For a wireless device in an RRC_Connectedstate, dedicated RRC signalling may be used for the request and deliveryof the other SI. For the wireless device in the RRC_Idle state and/or inthe RRC_Inactive state, the request may trigger a random accessprocedure.

A wireless device may report its radio access capability information,which may be static. A base station may request one or more indicationsof capabilities for a wireless device to report based on bandinformation. A temporary capability restriction request may be sent bythe wireless device (e.g., if allowed by a network) to signal thelimited availability of some capabilities (e.g., due to hardwaresharing, interference, and/or overheating) to the base station. The basestation may confirm or reject the request. The temporary capabilityrestriction may be transparent to 5GC (e.g., static capabilities may bestored in 5GC).

A wireless device may have an RRC connection with a network, forexample, if CA is configured. At RRC connection establishment,re-establishment, and/or handover procedures, a serving cell may provideNAS mobility information. At RRC connection re-establishment and/orhandover, a serving cell may provide a security input. This serving cellmay be referred to as the PCell. SCells may be configured to formtogether with the PCell a set of serving cells, for example, dependingon the capabilities of the wireless device. The configured set ofserving cells for the wireless device may comprise a PCell and one ormore SCells.

The reconfiguration, addition, and/or removal of SCells may be performedby RRC messaging. At intra-NR handover, RRC may add, remove, and/orreconfigure SCells for usage with the target PCell. Dedicated RRCsignaling may be used (e.g., if adding a new SCell) to send all requiredsystem information of the SCell (e.g., if in connected mode, wirelessdevices may not acquire broadcasted system information directly from theSCells).

The purpose of an RRC connection reconfiguration procedure may be tomodify an RRC connection, (e.g., to establish, modify, and/or releaseRBs; to perform handover; to setup, modify, and/or release measurements,for example, to add, modify, and/or release SCells and cell groups). NASdedicated information may be transferred from the network to thewireless device, for example, as part of the RRC connectionreconfiguration procedure. The RRCConnectionReconfiguration message maybe a command to modify an RRC connection. One or more RRC messages mayconvey information for measurement configuration, mobility control,and/or radio resource configuration (e.g., RBs, MAC main configuration,and/or physical channel configuration), which may comprise anyassociated dedicated NAS information and/or security configuration. Thewireless device may perform an SCell release, for example, if thereceived RRC Connection Reconfiguration message includes thesCellToReleaseList. The wireless device may perform SCell additions ormodification, for example, if the received RRC ConnectionReconfiguration message includes the sCellToAddModList.

An RRC connection establishment, reestablishment, and/or resumeprocedure may be to establish, reestablish, and/or resume an RRCconnection, respectively. An RRC connection establishment procedure maycomprise SRB1 establishment. The RRC connection establishment proceduremay be used to transfer the initial NAS dedicated information and/ormessage from a wireless device to an E-UTRAN. TheRRCConnectionReestablishment message may be used to re-establish SRB1.

A measurement report procedure may be used to transfer measurementresults from a wireless device to an NG-RAN. The wireless device mayinitiate a measurement report procedure, for example, after successfulsecurity activation. A measurement report message may be used to send(e.g., transmit) measurement results.

The wireless device 110 may comprise at least one communicationinterface 310 (e.g., a wireless modem, an antenna, and/or the like), atleast one processor 314, and at least one set of program codeinstructions 316 that may be stored in non-transitory memory 315 andexecutable by the at least one processor 314. The wireless device 110may further comprise at least one of at least one speaker and/ormicrophone 311, at least one keypad 312, at least one display and/ortouchpad 313, at least one power source 317, at least one globalpositioning system (GPS) chipset 318, and/or other peripherals 319.

The processor 314 of the wireless device 110, the processor 321A of thebase station 1 120A, and/or the processor 321B of the base station 2120B may comprise at least one of a general-purpose processor, a digitalsignal processor (DSP), a controller, a microcontroller, an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA) and/or other programmable logic device, discrete gate and/ortransistor logic, discrete hardware components, and/or the like. Theprocessor 314 of the wireless device 110, the processor 321A in basestation 1 120A, and/or the processor 321B in base station 2 120B mayperform at least one of signal coding and/or processing, dataprocessing, power control, input/output processing, and/or any otherfunctionality that may enable the wireless device 110, the base station1 120A and/or the base station 2 120B to operate in a wirelessenvironment.

The processor 314 of the wireless device 110 may be connected to and/orin communication with the speaker and/or microphone 311, the keypad 312,and/or the display and/or touchpad 313. The processor 314 may receiveuser input data from and/or provide user output data to the speakerand/or microphone 311, the keypad 312, and/or the display and/ortouchpad 313. The processor 314 in the wireless device 110 may receivepower from the power source 317 and/or may be configured to distributethe power to the other components in the wireless device 110. The powersource 317 may comprise at least one of one or more dry cell batteries,solar cells, fuel cells, and/or the like. The processor 314 may beconnected to the GPS chipset 318. The GPS chipset 318 may be configuredto provide geographic location information of the wireless device 110.

The processor 314 of the wireless device 110 may further be connected toand/or in communication with other peripherals 319, which may compriseone or more software and/or hardware modules that may provide additionalfeatures and/or functionalities. For example, the peripherals 319 maycomprise at least one of an accelerometer, a satellite transceiver, adigital camera, a universal serial bus (USB) port, a hands-free headset,a frequency modulated (FM) radio unit, a media player, an Internetbrowser, and/or the like.

The communication interface 320A of the base station 1, 120A, and/or thecommunication interface 320B of the base station 2, 120B, may beconfigured to communicate with the communication interface 310 of thewireless device 110, for example, via a wireless link 330A and/or via awireless link 330B, respectively. The communication interface 320A ofthe base station 1, 120A, may communicate with the communicationinterface 320B of the base station 2, 120B and/or other RAN and/or corenetwork nodes.

The wireless link 330A and/or the wireless link 330B may comprise atleast one of a bi-directional link and/or a directional link. Thecommunication interface 310 of the wireless device 110 may be configuredto communicate with the communication interface 320A of the base station1 120A and/or with the communication interface 320B of the base station2 120B. The base station 1 120A and the wireless device 110, and/or thebase station 2 120B and the wireless device 110, may be configured tosend and receive transport blocks, for example, via the wireless link330A and/or via the wireless link 330B, respectively. The wireless link330A and/or the wireless link 330B may use at least one frequencycarrier. Transceiver(s) may be used. A transceiver may be a device thatcomprises both a transmitter and a receiver. Transceivers may be used indevices such as wireless devices, base stations, relay nodes, computingdevices, and/or the like. Radio technology may be implemented in thecommunication interface 310, 320A, and/or 320B, and the wireless link330A and/or 330B. The radio technology may comprise one or more elementsshown in FIG. 4A, FIG. 4B, FIG. 4C, FIG. 4D, FIG. 6 , FIG. 7A, FIG. 7B,FIG. 8 , and associated text, described below.

Other nodes in a wireless network (e.g. AMF, UPF, SMF, etc.) maycomprise one or more communication interfaces, one or more processors,and memory storing instructions. A node (e.g., wireless device, basestation, AMF, SMF, UPF, servers, switches, antennas, and/or the like)may comprise one or more processors, and memory storing instructionsthat when executed by the one or more processors causes the node toperform certain processes and/or functions. Single-carrier and/ormulti-carrier communication operation may be performed. A non-transitorytangible computer readable media may comprise instructions executable byone or more processors to cause operation of single-carrier and/ormulti-carrier communications. An article of manufacture may comprise anon-transitory tangible computer readable machine-accessible mediumhaving instructions encoded thereon for enabling programmable hardwareto cause a node to enable operation of single-carrier and/ormulti-carrier communications. The node may include processors, memory,interfaces, and/or the like.

An interface may comprise at least one of a hardware interface, afirmware interface, a software interface, and/or a combination thereof.The hardware interface may comprise connectors, wires, and/or electronicdevices such as drivers, amplifiers, and/or the like. The softwareinterface may comprise code stored in a memory device to implementprotocol(s), protocol layers, communication drivers, device drivers,combinations thereof, and/or the like. The firmware interface maycomprise a combination of embedded hardware and/or code stored in(and/or in communication with) a memory device to implement connections,electronic device operations, protocol(s), protocol layers,communication drivers, device drivers, hardware operations, combinationsthereof, and/or the like.

A communication network may comprise the wireless device 110, the basestation 1, 120A, the base station 2, 120B, and/or any other device. Thecommunication network may comprise any number and/or type of devices,such as, for example, computing devices, wireless devices, mobiledevices, handsets, tablets, laptops, internet of things (IoT) devices,hotspots, cellular repeaters, computing devices, and/or, more generally,user equipment (e.g., UE). Although one or more of the above types ofdevices may be referenced herein (e.g., UE, wireless device, computingdevice, etc.), it should be understood that any device herein maycomprise any one or more of the above types of devices or similardevices. The communication network, and any other network referencedherein, may comprise an LTE network, a 5G network, or any other networkfor wireless communications. Apparatuses, systems, and/or methodsdescribed herein may generally be described as implemented on one ormore devices (e.g., wireless device, base station, eNB, gNB, computingdevice, etc.), in one or more networks, but it will be understood thatone or more features and steps may be implemented on any device and/orin any network. As used throughout, the term “base station” may compriseone or more of: a base station, a node, a Node B, a gNB, an eNB, anng-eNB, a relay node (e.g., an integrated access and backhaul (IAB)node), a donor node (e.g., a donor eNB, a donor gNB, etc.), an accesspoint (e.g., a WiFi access point), a computing device, a device capableof wirelessly communicating, or any other device capable of sendingand/or receiving signals. As used throughout, the term “wireless device”may comprise one or more of: a UE, a handset, a mobile device, acomputing device, a node, a device capable of wirelessly communicating,or any other device capable of sending and/or receiving signals. Anyreference to one or more of these terms/devices also considers use ofany other term/device mentioned above.

FIG. 4A, FIG. 4B, FIG. 4C and FIG. 4D show examples of uplink anddownlink signal transmission. FIG. 4A shows an example uplinktransmitter for at least one physical channel A baseband signalrepresenting a physical uplink shared channel may perform one or morefunctions. The one or more functions may comprise at least one of:scrambling (e.g., by Scrambling); modulation of scrambled bits togenerate complex-valued symbols (e.g., by a Modulation mapper); mappingof the complex-valued modulation symbols onto one or severaltransmission layers (e.g., by a Layer mapper); transform precoding togenerate complex-valued symbols (e.g., by a Transform precoder);precoding of the complex-valued symbols (e.g., by a Precoder); mappingof precoded complex-valued symbols to resource elements (e.g., by aResource element mapper); generation of complex-valued time-domainSingle Carrier-Frequency Division Multiple Access (SC-FDMA) or CP-OFDMsignal for an antenna port (e.g., by a signal gen.); and/or the like. ASC-FDMA signal for uplink transmission may be generated, for example, iftransform precoding is enabled. A CP-OFDM signal for uplink transmissionmay be generated by FIG. 4A, for example, if transform precoding is notenabled. These functions are shown as examples and other mechanisms maybe implemented.

FIG. 4B shows an example of modulation and up-conversion to the carrierfrequency of a complex-valued SC-FDMA or CP-OFDM baseband signal for anantenna port and/or for the complex-valued Physical Random AccessCHannel (PRACH) baseband signal. Filtering may be performed prior totransmission.

FIG. 4C shows an example of downlink transmissions. The baseband signalrepresenting a downlink physical channel may perform one or morefunctions. The one or more functions may comprise: scrambling of codedbits in a codeword to be transmitted on a physical channel (e.g., byScrambling); modulation of scrambled bits to generate complex-valuedmodulation symbols (e.g., by a Modulation mapper); mapping of thecomplex-valued modulation symbols onto one or several transmissionlayers (e.g., by a Layer mapper); precoding of the complex-valuedmodulation symbols on a layer for transmission on the antenna ports(e.g., by Precoding); mapping of complex-valued modulation symbols foran antenna port to resource elements (e.g., by a Resource elementmapper); generation of complex-valued time-domain OFDM signal for anantenna port (e.g., by an OFDM signal gen.); and/or the like. Thesefunctions are shown as examples and other mechanisms may be implemented.

A base station may send (e.g., transmit) a first symbol and a secondsymbol on an antenna port, to a wireless device. The wireless device mayinfer the channel (e.g., fading gain, multipath delay, etc.) forconveying the second symbol on the antenna port, from the channel forconveying the first symbol on the antenna port. A first antenna port anda second antenna port may be quasi co-located, for example, if one ormore large-scale properties of the channel over which a first symbol onthe first antenna port is conveyed may be inferred from the channel overwhich a second symbol on a second antenna port is conveyed. The one ormore large-scale properties may comprise at least one of: delay spread;Doppler spread; Doppler shift; average gain; average delay; and/orspatial receiving (Rx) parameters.

FIG. 4D shows an example modulation and up-conversion to the carrierfrequency of the complex-valued OFDM baseband signal for an antennaport. Filtering may be performed prior to transmission.

FIG. 5A shows example uplink channel mapping and example uplink physicalsignals. A physical layer may provide one or more information transferservices to a MAC and/or one or more higher layers. The physical layermay provide the one or more information transfer services to the MAC viaone or more transport channels. An information transfer service mayindicate how and/or with what characteristics data is transferred overthe radio interface.

Uplink transport channels may comprise an Uplink-Shared CHannel (UL-SCH)501 and/or a Random Access CHannel (RACH) 502. A wireless device maysend (e.g., transmit) one or more uplink DM-RSs 506 to a base stationfor channel estimation, for example, for coherent demodulation of one ormore uplink physical channels (e.g., PUSCH 503 and/or PUCCH 504). Thewireless device may send (e.g., transmit) to a base station at least oneuplink DM-RS 506 with PUSCH 503 and/or PUCCH 504, wherein the at leastone uplink DM-RS 506 may be spanning a same frequency range as acorresponding physical channel. The base station may configure thewireless device with one or more uplink DM-RS configurations. At leastone DM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). One or more additional uplink DM-RS may beconfigured to send (e.g., transmit) at one or more symbols of a PUSCHand/or PUCCH. The base station may semi-statically configure thewireless device with a maximum number of front-loaded DM-RS symbols forPUSCH and/or PUCCH. The wireless device may schedule a single-symbolDM-RS and/or double symbol DM-RS based on a maximum number offront-loaded DM-RS symbols, wherein the base station may configure thewireless device with one or more additional uplink DM-RS for PUSCHand/or PUCCH. A new radio network may support, for example, at least forCP-OFDM, a common DM-RS structure for DL and UL, wherein a DM-RSlocation, DM-RS pattern, and/or scrambling sequence may be same ordifferent.

Whether or not an uplink PT-RS 507 is present may depend on an RRCconfiguration. A presence of the uplink PT-RS may be wirelessdevice-specifically configured. A presence and/or a pattern of theuplink PT-RS 507 in a scheduled resource may be wirelessdevice-specifically configured by a combination of RRC signaling and/orassociation with one or more parameters used for other purposes (e.g.,Modulation and Coding Scheme (MCS)) which may be indicated by DCI. Ifconfigured, a dynamic presence of uplink PT-RS 507 may be associatedwith one or more DCI parameters comprising at least a MCS. A radionetwork may support a plurality of uplink PT-RS densities defined intime/frequency domain. If present, a frequency domain density may beassociated with at least one configuration of a scheduled bandwidth. Awireless device may assume a same precoding for a DMRS port and a PT-RSport. A number of PT-RS ports may be less than a number of DM-RS portsin a scheduled resource. The uplink PT-RS 507 may be confined in thescheduled time/frequency duration for a wireless device.

A wireless device may send (e.g., transmit) an SRS 508 to a base stationfor channel state estimation, for example, to support uplink channeldependent scheduling and/or link adaptation. The SRS 508 sent (e.g.,transmitted) by the wireless device may allow for the base station toestimate an uplink channel state at one or more different frequencies. Abase station scheduler may use an uplink channel state to assign one ormore resource blocks of a certain quality (e.g., above a qualitythreshold) for an uplink PUSCH transmission from the wireless device.The base station may semi-statically configure the wireless device withone or more SRS resource sets. For an SRS resource set, the base stationmay configure the wireless device with one or more SRS resources. An SRSresource set applicability may be configured by a higher layer (e.g.,RRC) parameter. An SRS resource in each of one or more SRS resource setsmay be sent (e.g., transmitted) at a time instant, for example, if ahigher layer parameter indicates beam management. The wireless devicemay send (e.g., transmit) one or more SRS resources in different SRSresource sets simultaneously. A new radio network may support aperiodic,periodic, and/or semi-persistent SRS transmissions. The wireless devicemay send (e.g., transmit) SRS resources, for example, based on one ormore trigger types. The one or more trigger types may comprise higherlayer signaling (e.g., RRC) and/or one or more DCI formats (e.g., atleast one DCI format may be used for a wireless device to select atleast one of one or more configured SRS resource sets). An SRS triggertype 0 may refer to an SRS triggered based on a higher layer signaling.An SRS trigger type 1 may refer to an SRS triggered based on one or moreDCI formats. The wireless device may be configured to send (e.g.,transmit) the SRS 508 after a transmission of PUSCH 503 andcorresponding uplink DM-RS 506, for example, if PUSCH 503 and the SRS508 are transmitted in a same slot.

A base station may semi-statically configure a wireless device with oneor more SRS configuration parameters indicating at least one offollowing: an SRS resource configuration identifier, a number of SRSports, time domain behavior of SRS resource configuration (e.g., anindication of periodic, semi-persistent, or aperiodic SRS), slot(mini-slot, and/or subframe) level periodicity and/or offset for aperiodic and/or aperiodic SRS resource, a number of OFDM symbols in aSRS resource, starting OFDM symbol of a SRS resource, an SRS bandwidth,a frequency hopping bandwidth, a cyclic shift, and/or an SRS sequenceID.

FIG. 5B shows an example downlink channel mapping and downlink physicalsignals. Downlink transport channels may comprise a Downlink-SharedCHannel (DL-SCH) 511, a Paging CHannel (PCH) 512, and/or a BroadcastCHannel (BCH) 513. A transport channel may be mapped to one or morecorresponding physical channels. A UL-SCH 501 may be mapped to aPhysical Uplink Shared CHannel (PUSCH) 503. A RACH 502 may be mapped toa PRACH 505. A DL-SCH 511 and a PCH 512 may be mapped to a PhysicalDownlink Shared CHannel (PDSCH) 514. A BCH 513 may be mapped to aPhysical Broadcast CHannel (PBCH) 516.

A radio network may comprise one or more downlink and/or uplinktransport channels. The radio network may comprise one or more physicalchannels without a corresponding transport channel. The one or morephysical channels may be used for an Uplink Control Information (UCI)509 and/or a Downlink Control Information (DCI) 517. A Physical UplinkControl CHannel (PUCCH) 504 may carry UCI 509 from a wireless device toa base station. A Physical Downlink Control CHannel (PDCCH) 515 maycarry the DCI 517 from a base station to a wireless device. The radionetwork (e.g., NR) may support the UCI 509 multiplexing in the PUSCH503, for example, if the UCI 509 and the PUSCH 503 transmissions maycoincide in a slot (e.g., at least in part). The UCI 509 may comprise atleast one of a CSI, an Acknowledgement (ACK)/Negative Acknowledgement(NACK), and/or a scheduling request. The DCI 517 via the PDCCH 515 mayindicate at least one of following: one or more downlink assignmentsand/or one or more uplink scheduling grants.

In uplink, a wireless device may send (e.g., transmit) one or moreReference Signals (RSs) to a base station. The one or more RSs maycomprise at least one of a Demodulation-RS (DM-RS) 506, a PhaseTracking-RS (PT-RS) 507, and/or a Sounding RS (SRS) 508. In downlink, abase station may send (e.g., transmit, unicast, multicast, and/orbroadcast) one or more RSs to a wireless device. The one or more RSs maycomprise at least one of a Primary Synchronization Signal(PSS)/Secondary Synchronization Signal (SSS) 521, a CSI-RS 522, a DM-RS523, and/or a PT-RS 524.

In a time domain, an SS/PBCH block may comprise one or more OFDM symbols(e.g., 4 OFDM symbols numbered in increasing order from 0 to 3) withinthe SS/PBCH block. An SS/PBCH block may comprise the PSS/SSS 521 and/orthe PBCH 516. In the frequency domain, an SS/PBCH block may comprise oneor more contiguous subcarriers (e.g., 240 contiguous subcarriers withthe subcarriers numbered in increasing order from 0 to 239) within theSS/PBCH block. The PSS/SSS 521 may occupy, for example, 1 OFDM symboland 127 subcarriers. The PBCH 516 may span across, for example, 3 OFDMsymbols and 240 subcarriers. A wireless device may assume that one ormore SS/PBCH blocks transmitted with a same block index may be quasico-located, for example, with respect to Doppler spread, Doppler shift,average gain, average delay, and/or spatial Rx parameters. A wirelessdevice may not assume quasi co-location for other SS/PBCH blocktransmissions. A periodicity of an SS/PBCH block may be configured by aradio network (e.g., by an RRC signaling). One or more time locations inwhich the SS/PBCH block may be sent may be determined by sub-carrierspacing. A wireless device may assume a band-specific sub-carrierspacing for an SS/PBCH block, for example, unless a radio network hasconfigured the wireless device to assume a different sub-carrierspacing.

The downlink CSI-RS 522 may be used for a wireless device to acquirechannel state information. A radio network may support periodic,aperiodic, and/or semi-persistent transmission of the downlink CSI-RS522. A base station may semi-statically configure and/or reconfigure awireless device with periodic transmission of the downlink CSI-RS 522. Aconfigured CSI-RS resources may be activated and/or deactivated. Forsemi-persistent transmission, an activation and/or deactivation of aCSI-RS resource may be triggered dynamically. A CSI-RS configuration maycomprise one or more parameters indicating at least a number of antennaports. A base station may configure a wireless device with 32 ports, orany other number of ports. A base station may semi-statically configurea wireless device with one or more CSI-RS resource sets. One or moreCSI-RS resources may be allocated from one or more CSI-RS resource setsto one or more wireless devices. A base station may semi-staticallyconfigure one or more parameters indicating CSI RS resource mapping, forexample, time-domain location of one or more CSI-RS resources, abandwidth of a CSI-RS resource, and/or a periodicity. A wireless devicemay be configured to use the same OFDM symbols for the downlink CSI-RS522 and the Control Resource Set (CORESET), for example, if the downlinkCSI-RS 522 and the CORESET are spatially quasi co-located and resourceelements associated with the downlink CSI-RS 522 are the outside of PRBsconfigured for the CORESET. A wireless device may be configured to usethe same OFDM symbols for downlink CSI-RS 522 and SS/PBCH blocks, forexample, if the downlink CSI-RS 522 and SS/PBCH blocks are spatiallyquasi co-located and resource elements associated with the downlinkCSI-RS 522 are outside of the PRBs configured for the SS/PBCH blocks.

A wireless device may send (e.g., transmit) one or more downlink DM-RSs523 to a base station for channel estimation, for example, for coherentdemodulation of one or more downlink physical channels (e.g., PDSCH514). A radio network may support one or more variable and/orconfigurable DM-RS patterns for data demodulation. At least one downlinkDM-RS configuration may support a front-loaded DM-RS pattern. Afront-loaded DM-RS may be mapped over one or more OFDM symbols (e.g., 1or 2 adjacent OFDM symbols). A base station may semi-staticallyconfigure a wireless device with a maximum number of front-loaded DM-RSsymbols for PDSCH 514. A DM-RS configuration may support one or moreDM-RS ports. A DM-RS configuration may support at least 8 orthogonaldownlink DM-RS ports, for example, for single user-MIMO. ADM-RSconfiguration may support 12 orthogonal downlink DM-RS ports, forexample, for multiuser-MIMO. A radio network may support, for example,at least for CP-OFDM, a common DM-RS structure for DL and UL, wherein aDM-RS location, DM-RS pattern, and/or scrambling sequence may be thesame or different.

Whether or not the downlink PT-RS 524 is present may depend on an RRCconfiguration. A presence of the downlink PT-RS 524 may be wirelessdevice-specifically configured. A presence and/or a pattern of thedownlink PT-RS 524 in a scheduled resource may be wirelessdevice-specifically configured, for example, by a combination of RRCsignaling and/or an association with one or more parameters used forother purposes (e.g., MCS) which may be indicated by the DCI. Ifconfigured, a dynamic presence of the downlink PT-RS 524 may beassociated with one or more DCI parameters comprising at least MCS. Aradio network may support a plurality of PT-RS densities in atime/frequency domain. If present, a frequency domain density may beassociated with at least one configuration of a scheduled bandwidth. Awireless device may assume the same precoding for a DMRS port and aPT-RS port. A number of PT-RS ports may be less than a number of DM-RSports in a scheduled resource. The downlink PT-RS 524 may be confined inthe scheduled time/frequency duration for a wireless device.

FIG. 6 shows an example transmission time and reception time for acarrier. A multicarrier OFDM communication system may include one ormore carriers, for example, ranging from 1 to 32 carriers (such as forcarrier aggregation) or ranging from 1 to 64 carriers (such as for dualconnectivity). Different radio frame structures may be supported (e.g.,for FDD and/or for TDD duplex mechanisms). FIG. 6 shows an example frametiming. Downlink and uplink transmissions may be organized into radioframes 601. Radio frame duration may be 10 milliseconds (ms). A 10 msradio frame 601 may be divided into ten equally sized subframes 602,each with a 1 ms duration. Subframe(s) may comprise one or more slots(e.g., slots 603 and 605) depending on subcarrier spacing and/or CPlength. For example, a subframe with 15 kHz, 30 kHz, 60 kHz, 120 kHz,240 kHz and 480 kHz subcarrier spacing may comprise one, two, four,eight, sixteen and thirty-two slots, respectively. In FIG. 6 , asubframe may be divided into two equally sized slots 603 with 0.5 msduration. For example, 10 subframes may be available for downlinktransmission and 10 subframes may be available for uplink transmissionsin a 10 ms interval. Other subframe durations such as, for example, 0.5ms, 1 ms, 2 ms, and 5 ms may be supported. Uplink and downlinktransmissions may be separated in the frequency domain. Slot(s) mayinclude a plurality of OFDM symbols 604. The number of OFDM symbols 604in a slot 605 may depend on the cyclic prefix length. A slot may be 14OFDM symbols for the same subcarrier spacing of up to 480 kHz withnormal CP. A slot may be 12 OFDM symbols for the same subcarrier spacingof 60 kHz with extended CP. A slot may comprise downlink, uplink, and/ora downlink part and an uplink part, and/or alike.

FIG. 7A shows example sets of OFDM subcarriers. A base station maycommunicate with a wireless device using a carrier having an examplechannel bandwidth 700. Arrow(s) in the example may depict a subcarrierin a multicarrier OFDM system. The OFDM system may use technology suchas OFDM technology, SC-FDMA technology, and/or the like. An arrow 701shows a subcarrier transmitting information symbols. A subcarrierspacing 702, between two contiguous subcarriers in a carrier, may be anyone of 15 kHz, 30 kHz, 60 kHz, 120 kHz, 240 kHz, or any other frequency.Different subcarrier spacing may correspond to different transmissionnumerologies. A transmission numerology may comprise at least: anumerology index; a value of subcarrier spacing; and/or a type of cyclicprefix (CP). A base station may send (e.g., transmit) to and/or receivefrom a wireless device via a number of subcarriers 703 in a carrier. Abandwidth occupied by a number of subcarriers 703 (e.g., transmissionbandwidth) may be smaller than the channel bandwidth 700 of a carrier,for example, due to guard bands 704 and 705. Guard bands 704 and 705 maybe used to reduce interference to and from one or more neighborcarriers. A number of subcarriers (e.g., transmission bandwidth) in acarrier may depend on the channel bandwidth of the carrier and/or thesubcarrier spacing. A transmission bandwidth, for a carrier with a 20MHz channel bandwidth and a 15 kHz subcarrier spacing, may be in numberof 1024 subcarriers.

A base station and a wireless device may communicate with multiplecomponent carriers (CCs), for example, if configured with CA. Differentcomponent carriers may have different bandwidth and/or differentsubcarrier spacing, for example, if CA is supported. A base station maysend (e.g., transmit) a first type of service to a wireless device via afirst component carrier. The base station may send (e.g., transmit) asecond type of service to the wireless device via a second componentcarrier. Different types of services may have different servicerequirements (e.g., data rate, latency, reliability), which may besuitable for transmission via different component carriers havingdifferent subcarrier spacing and/or different bandwidth.

FIG. 7B shows examples of component carriers. A first component carriermay comprise a first number of subcarriers 706 having a first subcarrierspacing 709. A second component carrier may comprise a second number ofsubcarriers 707 having a second subcarrier spacing 710. A thirdcomponent carrier may comprise a third number of subcarriers 708 havinga third subcarrier spacing 711. Carriers in a multicarrier OFDMcommunication system may be contiguous carriers, non-contiguouscarriers, or a combination of both contiguous and non-contiguouscarriers.

FIG. 8 shows an example of OFDM radio resources. A carrier may have atransmission bandwidth 801. A resource grid may be in a structure offrequency domain 802 and time domain 803. A resource grid may comprise afirst number of OFDM symbols in a subframe and a second number ofresource blocks, starting from a common resource block indicated byhigher-layer signaling (e.g., RRC signaling), for a transmissionnumerology and a carrier. In a resource grid, a resource element 805 maycomprise a resource unit that may be identified by a subcarrier indexand a symbol index. A subframe may comprise a first number of OFDMsymbols 807 that may depend on a numerology associated with a carrier. Asubframe may have 14 OFDM symbols for a carrier, for example, if asubcarrier spacing of a numerology of a carrier is 15 kHz. A subframemay have 28 OFDM symbols, for example, if a subcarrier spacing of anumerology is 30 kHz. A subframe may have 56 OFDM symbols, for example,if a subcarrier spacing of a numerology is 60 kHz. A subcarrier spacingof a numerology may comprise any other frequency. A second number ofresource blocks comprised in a resource grid of a carrier may depend ona bandwidth and a numerology of the carrier.

A resource block 806 may comprise 12 subcarriers. Multiple resourceblocks may be grouped into a Resource Block Group (RBG) 804. A size of aRBG may depend on at least one of: a RRC message indicating a RBG sizeconfiguration; a size of a carrier bandwidth; and/or a size of abandwidth part of a carrier. A carrier may comprise multiple bandwidthparts. A first bandwidth part of a carrier may have a differentfrequency location and/or a different bandwidth from a second bandwidthpart of the carrier.

A base station may send (e.g., transmit), to a wireless device, adownlink control information comprising a downlink or uplink resourceblock assignment. A base station may send (e.g., transmit) to and/orreceive from, a wireless device, data packets (e.g., transport blocks).The data packets may be scheduled on and transmitted via one or moreresource blocks and one or more slots indicated by parameters indownlink control information and/or RRC message(s). A starting symbolrelative to a first slot of the one or more slots may be indicated tothe wireless device. A base station may send (e.g., transmit) to and/orreceive from, a wireless device, data packets. The data packets may bescheduled for transmission on one or more RBGs and in one or more slots.

A base station may send (e.g., transmit), to a wireless device, downlinkcontrol information comprising a downlink assignment. The base stationmay send (e.g., transmit) the DCI via one or more PDCCHs. The downlinkassignment may comprise parameters indicating at least one of amodulation and coding format; resource allocation; and/or HARQinformation related to the DL-SCH. The resource allocation may compriseparameters of resource block allocation; and/or slot allocation. A basestation may allocate (e.g., dynamically) resources to a wireless device,for example, via a Cell-Radio Network Temporary Identifier (C-RNTI) onone or more PDCCHs. The wireless device may monitor the one or morePDCCHs, for example, in order to find possible allocation if itsdownlink reception is enabled. The wireless device may receive one ormore downlink data packets on one or more PDSCH scheduled by the one ormore PDCCHs, for example, if the wireless device successfully detectsthe one or more PDCCHs.

A base station may allocate Configured Scheduling (CS) resources fordown link transmission to a wireless device. The base station may send(e.g., transmit) one or more RRC messages indicating a periodicity ofthe CS grant. The base station may send (e.g., transmit) DCI via a PDCCHaddressed to a Configured Scheduling-RNTI (CS-RNTI) activating the CSresources. The DCI may comprise parameters indicating that the downlinkgrant is a CS grant. The CS grant may be implicitly reused according tothe periodicity defined by the one or more RRC messages. The CS grantmay be implicitly reused, for example, until deactivated.

A base station may send (e.g., transmit), to a wireless device via oneor more PDCCHs, downlink control information comprising an uplink grant.The uplink grant may comprise parameters indicating at least one of amodulation and coding format; a resource allocation; and/or HARQinformation related to the UL-SCH. The resource allocation may compriseparameters of resource block allocation; and/or slot allocation. Thebase station may dynamically allocate resources to the wireless devicevia a C-RNTI on one or more PDCCHs. The wireless device may monitor theone or more PDCCHs, for example, in order to find possible resourceallocation. The wireless device may send (e.g., transmit) one or moreuplink data packets via one or more PUSCH scheduled by the one or morePDCCHs, for example, if the wireless device successfully detects the oneor more PDCCHs.

The base station may allocate CS resources for uplink data transmissionto a wireless device. The base station may transmit one or more RRCmessages indicating a periodicity of the CS grant. The base station maysend (e.g., transmit) DCI via a PDCCH addressed to a CS-RNTI to activatethe CS resources. The DCI may comprise parameters indicating that theuplink grant is a CS grant. The CS grant may be implicitly reusedaccording to the periodicity defined by the one or more RRC message, TheCS grant may be implicitly reused, for example, until deactivated.

A base station may send (e.g., transmit) DCI and/or control signalingvia a PDCCH. The DCI may comprise a format of a plurality of formats.The DCI may comprise downlink and/or uplink scheduling information(e.g., resource allocation information, HARQ related parameters, MCS),request(s) for CSI (e.g., aperiodic CQI reports), request(s) for an SRS,uplink power control commands for one or more cells, one or more timinginformation (e.g., TB transmission/reception timing, HARQ feedbacktiming, etc.), and/or the like. The DCI may indicate an uplink grantcomprising transmission parameters for one or more transport blocks. TheDCI may indicate a downlink assignment indicating parameters forreceiving one or more transport blocks. The DCI may be used by the basestation to initiate a contention-free random access at the wirelessdevice. The base station may send (e.g., transmit) DCI comprising a slotformat indicator (SFI) indicating a slot format. The base station maysend (e.g., transmit) DCI comprising a pre-emption indication indicatingthe PRB(s) and/or OFDM symbol(s) in which a wireless device may assumeno transmission is intended for the wireless device. The base stationmay send (e.g., transmit) DCI for group power control of the PUCCH, thePUSCH, and/or an SRS. DCI may correspond to an RNTI. The wireless devicemay obtain an RNTI after or in response to completing the initial access(e.g., C-RNTI). The base station may configure an RNTI for the wireless(e.g., CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI,TPC-SRS-RNTI, etc.). The wireless device may determine (e.g., compute)an RNTI (e.g., the wireless device may determine the RA-RNTI based onresources used for transmission of a preamble). An RNTI may have apre-configured value (e.g., P-RNTI or SI-RNTI). The wireless device maymonitor a group common search space which may be used by the basestation for sending (e.g., transmitting) DCIs that are intended for agroup of wireless devices. A group common DCI may correspond to an RNTIwhich is commonly configured for a group of wireless devices. Thewireless device may monitor a wireless device-specific search space. Awireless device specific DCI may correspond to an RNTI configured forthe wireless device.

A communications system (e.g., an NR system) may support a single beamoperation and/or a multi-beam operation. In a multi-beam operation, abase station may perform a downlink beam sweeping to provide coveragefor common control channels and/or downlink SS blocks, which maycomprise at least a PSS, a SSS, and/or PBCH. A wireless device maymeasure quality of a beam pair link using one or more RSs. One or moreSS blocks, or one or more CSI-RS resources (e.g., which may beassociated with a CSI-RS resource index (CRI)), and/or one or moreDM-RSs of a PBCH, may be used as an RS for measuring a quality of a beampair link. The quality of a beam pair link may be based on a referencesignal received power (RSRP) value, a reference signal received quality(RSRQ) value, and/or a CSI value measured on RS resources. The basestation may indicate whether an RS resource, used for measuring a beampair link quality, is quasi-co-located (QCLed) with DM-RSs of a controlchannel. An RS resource and DM-RSs of a control channel may be calledQCLed, for example, if channel characteristics from a transmission on anRS to a wireless device, and that from a transmission on a controlchannel to a wireless device, are similar or the same under a configuredcriterion. In a multi-beam operation, a wireless device may perform anuplink beam sweeping to access a cell.

A wireless device may be configured to monitor a PDCCH on one or morebeam pair links simultaneously, for example, depending on a capabilityof the wireless device. This monitoring may increase robustness againstbeam pair link blocking. A base station may send (e.g., transmit) one ormore messages to configure the wireless device to monitor the PDCCH onone or more beam pair links in different PDCCH OFDM symbols. A basestation may send (e.g., transmit) higher layer signaling (e.g., RRCsignaling) and/or a MAC CE comprising parameters related to the Rx beamsetting of the wireless device for monitoring the PDCCH on one or morebeam pair links. The base station may send (e.g., transmit) anindication of a spatial QCL assumption between an DL RS antenna port(s)(e.g., a cell-specific CSI-RS, a wireless device-specific CSI-RS, an SSblock, and/or a PBCH with or without DM-RSs of the PBCH) and/or DL RSantenna port(s) for demodulation of a DL control channel. Signaling forbeam indication for a PDCCH may comprise MAC CE signaling, RRCsignaling, DCI signaling, and/or specification-transparent and/orimplicit method, and/or any combination of signaling methods.

A base station may indicate spatial QCL parameters between DL RS antennaport(s) and DM-RS antenna port(s) of a DL data channel, for example, forreception of a unicast DL data channel. The base station may send (e.g.,transmit) DCI (e.g., downlink grants) comprising information indicatingthe RS antenna port(s). The information may indicate RS antenna port(s)that may be QCL-ed with the DM-RS antenna port(s). A different set ofDM-RS antenna port(s) for a DL data channel may be indicated as QCL witha different set of the RS antenna port(s).

FIG. 9A shows an example of beam sweeping in a DL channel. In anRRC_INACTIVE state or RRC_IDLE state, a wireless device may assume thatSS blocks form an SS burst 940, and an SS burst set 950. The SS burstset 950 may have a given periodicity. A base station 120 may send (e.g.,transmit) SS blocks in multiple beams, together forming a SS burst 940,for example, in a multi-beam operation. One or more SS blocks may besent (e.g., transmitted) on one beam. If multiple SS bursts 940 aretransmitted with multiple beams, SS bursts together may form SS burstset 950.

A wireless device may use CSI-RS for estimating a beam quality of a linkbetween a wireless device and a base station, for example, in the multibeam operation. A beam may be associated with a CSI-RS. A wirelessdevice may (e.g., based on a RSRP measurement on CSI-RS) report a beamindex, which may be indicated in a CRI for downlink beam selectionand/or associated with an RSRP value of a beam. A CSI-RS may be sent(e.g., transmitted) on a CSI-RS resource, which may comprise at leastone of: one or more antenna ports and/or one or more time and/orfrequency radio resources. A CSI-RS resource may be configured in acell-specific way such as by common RRC signaling, or in a wirelessdevice-specific way such as by dedicated RRC signaling and/or L1/L2signaling. Multiple wireless devices covered by a cell may measure acell-specific CSI-RS resource. A dedicated subset of wireless devicescovered by a cell may measure a wireless device-specific CSI-RSresource.

A CSI-RS resource may be sent (e.g., transmitted) periodically, usingaperiodic transmission, or using a multi-shot or semi-persistenttransmission. In a periodic transmission in FIG. 9A, a base station 120may send (e.g., transmit) configured CSI-RS resources 940 periodicallyusing a configured periodicity in a time domain. In an aperiodictransmission, a configured CSI-RS resource may be sent (e.g.,transmitted) in a dedicated time slot. In a multi-shot and/orsemi-persistent transmission, a configured CSI-RS resource may be sent(e.g., transmitted) within a configured period. Beams used for CSI-RStransmission may have a different beam width than beams used forSS-blocks transmission.

FIG. 9B shows an example of a beam management procedure, such as in anexample new radio network. The base station 120 and/or the wirelessdevice 110 may perform a downlink L1/L2 beam management procedure. Oneor more of the following downlink L1/L2 beam management procedures maybe performed within one or more wireless devices 110 and one or morebase stations 120. A P1 procedure 910 may be used to enable the wirelessdevice 110 to measure one or more Transmission (Tx) beams associatedwith the base station 120, for example, to support a selection of afirst set of Tx beams associated with the base station 120 and a firstset of Rx beam(s) associated with the wireless device 110. A basestation 120 may sweep a set of different Tx beams, for example, forbeamforming at a base station 120 (such as shown in the top row, in acounter-clockwise direction). A wireless device 110 may sweep a set ofdifferent Rx beams, for example, for beamforming at a wireless device110 (such as shown in the bottom row, in a clockwise direction). A P2procedure 920 may be used to enable a wireless device 110 to measure oneor more Tx beams associated with a base station 120, for example, topossibly change a first set of Tx beams associated with a base station120. A P2 procedure 920 may be performed on a possibly smaller set ofbeams (e.g., for beam refinement) than in the P1 procedure 910. A P2procedure 920 may be a special example of a P1 procedure 910. A P3procedure 930 may be used to enable a wireless device 110 to measure atleast one Tx beam associated with a base station 120, for example, tochange a first set of Rx beams associated with a wireless device 110.

A wireless device 110 may send (e.g., transmit) one or more beammanagement reports to a base station 120. In one or more beam managementreports, a wireless device 110 may indicate one or more beam pairquality parameters comprising one or more of: a beam identification; anRSRP; a Precoding Matrix Indicator (PMI), Channel Quality Indicator(CQI), and/or Rank Indicator (RI) of a subset of configured beams. Basedon one or more beam management reports, the base station 120 may send(e.g., transmit) to a wireless device 110 a signal indicating that oneor more beam pair links are one or more serving beams. The base station120 may send (e.g., transmit) the PDCCH and the PDSCH for a wirelessdevice 110 using one or more serving beams.

A communications network (e.g., a new radio network) may support aBandwidth Adaptation (BA). Receive and/or transmit bandwidths that maybe configured for a wireless device using a BA may not be large. Receiveand/or transmit bandwidth may not be as large as a bandwidth of a cell.Receive and/or transmit bandwidths may be adjustable. A wireless devicemay change receive and/or transmit bandwidths, for example, to reduce(e.g., shrink) the bandwidth(s) at (e.g., during) a period of lowactivity such as to save power. A wireless device may change a locationof receive and/or transmit bandwidths in a frequency domain, forexample, to increase scheduling flexibility. A wireless device maychange a subcarrier spacing, for example, to allow different services.

A Bandwidth Part (BWP) may comprise a subset of a total cell bandwidthof a cell. A base station may configure a wireless device with one ormore BWPs, for example, to achieve a BA. A base station may indicate, toa wireless device, which of the one or more (configured) BWPs is anactive BWP.

FIG. 10 shows an example of BWP configurations. BWPs may be configuredas follows: BWP1 (1010 and 1050) with a width of 40 MHz and subcarrierspacing of 15 kHz; BWP2 (1020 and 1040) with a width of 10 MHz andsubcarrier spacing of 15 kHz; BWP3 1030 with a width of 20 MHz andsubcarrier spacing of 60 kHz. Any number of BWP configurations maycomprise any other width and subcarrier spacing combination.

A wireless device, configured for operation in one or more BWPs of acell, may be configured by one or more higher layers (e.g., RRC layer).The wireless device may be configured for a cell with: a set of one ormore BWPs (e.g., at most four BWPs) for reception (e.g., a DL BWP set)in a DL bandwidth by at least one parameter DL-BWP; and a set of one ormore BWPs (e.g., at most four BWPs) for transmissions (e.g., UL BWP set)in an UL bandwidth by at least one parameter UL-BWP. BWPs are describedas example resources. Any wireless resource may be applicable to one ormore procedures described herein.

A base station may configure a wireless device with one or more UL andDL BWP pairs, for example, to enable BA on the PCell. To enable BA onSCells (e.g., for CA), a base station may configure a wireless device atleast with one or more DL BWPs (e.g., there may be none in an UL).

An initial active DL BWP may comprise at least one of a location andnumber of contiguous PRBs, a subcarrier spacing, or a cyclic prefix, forexample, for a control resource set for at least one common searchspace. For operation on the PCell, one or more higher layer parametersmay indicate at least one initial UL BWP for a random access procedure.If a wireless device is configured with a secondary carrier on a primarycell, the wireless device may be configured with an initial BWP forrandom access procedure on a secondary carrier.

A wireless device may expect that a center frequency for a DL BWP may besame as a center frequency for a UL BWP, for example, for unpairedspectrum operation. A base station may semi-statically configure awireless device for a cell with one or more parameters, for example, fora DL BWP or an UL BWP in a set of one or more DL BWPs or one or more ULBWPs, respectively. The one or more parameters may indicate one or moreof following: a subcarrier spacing; a cyclic prefix; a number ofcontiguous PRBs; an index in the set of one or more DL BWPs and/or oneor more UL BWPs; a link between a DL BWP and an UL BWP from a set ofconfigured DL BWPs and UL BWPs; a DCI detection to a PDSCH receptiontiming; a PDSCH reception to a HARQ-ACK transmission timing value; a DCIdetection to a PUSCH transmission timing value; and/or an offset of afirst PRB of a DL bandwidth or an UL bandwidth, respectively, relativeto a first PRB of a bandwidth.

For a DL BWP in a set of one or more DL BWPs on a PCell, a base stationmay configure a wireless device with one or more control resource setsfor at least one type of common search space and/or one wirelessdevice-specific search space. A base station may refrain fromconfiguring a wireless device without a common search space on a PCell,or on a PSCell, in an active DL BWP. For an UL BWP in a set of one ormore UL BWPs, a base station may configure a wireless device with one ormore resource sets for one or more PUCCH transmissions.

DCI may comprise a BWP indicator field. The BWP indicator field valuemay indicate an active DL BWP, from a configured DL BWP set, for one ormore DL receptions. The BWP indicator field value may indicate an activeUL BWP, from a configured UL BWP set, for one or more UL transmissions.

For a PCell, a base station may semi-statically configure a wirelessdevice with a default DL BWP among configured DL BWPs. If a wirelessdevice is not provided with a default DL BWP, a default BWP may be aninitial active DL BWP. A default BWP may not be configured for one ormore wireless devices. A first (or initial) BWP may serve as a defaultBWP, for example, if a default BWP is not configured.

A base station may configure a wireless device with a timer value for aPCell. A wireless device may start a timer (e.g., a BWP inactivitytimer), for example, if a wireless device detects DCI indicating anactive DL BWP, other than a default DL BWP, for a paired spectrumoperation, and/or if a wireless device detects DCI indicating an activeDL BWP or UL BWP, other than a default DL BWP or UL BWP, for an unpairedspectrum operation. The wireless device may increment the timer by aninterval of a first value (e.g., the first value may be 1 millisecond,0.5 milliseconds, or any other time duration), for example, if thewireless device does not detect DCI at (e.g., during) the interval for apaired spectrum operation or for an unpaired spectrum operation. Thetimer may expire at a time that the timer is equal to the timer value. Awireless device may switch to the default DL BWP from an active DL BWP,for example, if the timer expires.

A base station may semi-statically configure a wireless device with oneor more BWPs. A wireless device may switch an active BWP from a firstBWP to a second BWP, for example, after or in response to receiving DCIindicating the second BWP as an active BWP, and/or after or in responseto an expiry of BWP inactivity timer (e.g., the second BWP may be adefault BWP). FIG. 10 shows an example of three BWPs configured, BWP1(1010 and 1050), BWP2 (1020 and 1040), and BWP3 (1030). BWP2 (1020 and1040) may be a default BWP. BWP1 (1010) may be an initial active BWP. Awireless device may switch an active BWP from BWP1 1010 to BWP2 1020,for example, after or in response to an expiry of the BWP inactivitytimer. A wireless device may switch an active BWP from BWP2 1020 to BWP31030, for example, after or in response to receiving DCI indicating BWP31030 as an active BWP. Switching an active BWP from BWP3 1030 to BWP21040 and/or from BWP2 1040 to BWP1 1050 may be after or in response toreceiving DCI indicating an active BWP, and/or after or in response toan expiry of BWP inactivity timer.

Wireless device procedures on a secondary cell may be same as on aprimary cell using the timer value for the secondary cell and thedefault DL BWP for the secondary cell, for example, if a wireless deviceis configured for a secondary cell with a default DL BWP amongconfigured DL BWPs and a timer value. A wireless device may use anindicated DL BWP and an indicated UL BWP on a secondary cell as arespective first active DL BWP and first active UL BWP on a secondarycell or carrier, for example, if a base station configures a wirelessdevice with a first active DL BWP and a first active UL BWP on asecondary cell or carrier.

FIG. 11A and FIG. 11B show packet flows using a multi connectivity(e.g., dual connectivity, multi connectivity, tight interworking, and/orthe like). FIG. 11A shows an example of a protocol structure of awireless device 110 (e.g., UE) with CA and/or multi connectivity. FIG.11B shows an example of a protocol structure of multiple base stationswith CA and/or multi connectivity. The multiple base stations maycomprise a master node, MN 1130 (e.g., a master node, a master basestation, a master gNB, a master eNB, and/or the like) and a secondarynode, SN 1150 (e.g., a secondary node, a secondary base station, asecondary gNB, a secondary eNB, and/or the like). A master node 1130 anda secondary node 1150 may co-work to communicate with a wireless device110.

If multi connectivity is configured for a wireless device 110, thewireless device 110, which may support multiple reception and/ortransmission functions in an RRC connected state, may be configured toutilize radio resources provided by multiple schedulers of a multiplebase stations. Multiple base stations may be inter-connected via anon-ideal or ideal backhaul (e.g., Xn interface, X2 interface, and/orthe like). A base station involved in multi connectivity for a certainwireless device may perform at least one of two different roles: a basestation may act as a master base station or act as a secondary basestation. In multi connectivity, a wireless device may be connected toone master base station and one or more secondary base stations. Amaster base station (e.g., the MN 1130) may provide a master cell group(MCG) comprising a primary cell and/or one or more secondary cells for awireless device (e.g., the wireless device 110). A secondary basestation (e.g., the SN 1150) may provide a secondary cell group (SCG)comprising a primary secondary cell (PSCell) and/or one or moresecondary cells for a wireless device (e.g., the wireless device 110).

In multi connectivity, a radio protocol architecture that a bearer usesmay depend on how a bearer is setup. Three different types of bearersetup options may be supported: an MCG bearer, an SCG bearer, and/or asplit bearer. A wireless device may receive and/or send (e.g., transmit)packets of an MCG bearer via one or more cells of the MCG. A wirelessdevice may receive and/or send (e.g., transmit) packets of an SCG bearervia one or more cells of an SCG. Multi-connectivity may indicate havingat least one bearer configured to use radio resources provided by thesecondary base station. Multi-connectivity may or may not be configuredand/or implemented.

A wireless device (e.g., wireless device 110) may send (e.g., transmit)and/or receive: packets of an MCG bearer via an SDAP layer (e.g., SDAP1110), a PDCP layer (e.g., NR PDCP 1111), an RLC layer (e.g., MN RLC1114), and a MAC layer (e.g., MN MAC 1118); packets of a split bearervia an SDAP layer (e.g., SDAP 1110), a PDCP layer (e.g., NR PDCP 1112),one of a master or secondary RLC layer (e.g., MN RLC 1115, SN RLC 1116),and one of a master or secondary MAC layer (e.g., MN MAC 1118, SN MAC1119); and/or packets of an SCG bearer via an SDAP layer (e.g., SDAP1110), a PDCP layer (e.g., NR PDCP 1113), an RLC layer (e.g., SN RLC1117), and a MAC layer (e.g., MN MAC 1118).

A master base station (e.g., MN 1130) and/or a secondary base station(e.g., SN 1150) may send (e.g., transmit) and/or receive: packets of anMCG bearer via a master or secondary node SDAP layer (e.g., SDAP 1120,SDAP 1140), a master or secondary node PDCP layer (e.g., NR PDCP 1121,NR PDCP 1142), a master node RLC layer (e.g., MN RLC 1124, MN RLC 1125),and a master node MAC layer (e.g., MN MAC 1128); packets of an SCGbearer via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g., NR PDCP 1122, NRPDCP 1143), a secondary node RLC layer (e.g., SN RLC 1146, SN RLC 1147),and a secondary node MAC layer (e.g., SN MAC 1148); packets of a splitbearer via a master or secondary node SDAP layer (e.g., SDAP 1120, SDAP1140), a master or secondary node PDCP layer (e.g., NR PDCP 1123, NRPDCP 1141), a master or secondary node RLC layer (e.g., MN RLC 1126, SNRLC 1144, SN RLC 1145, MN RLC 1127), and a master or secondary node MAClayer (e.g., MN MAC 1128, SN MAC 1148).

In multi connectivity, a wireless device may configure multiple MACentities, such as one MAC entity (e.g., MN MAC 1118) for a master basestation, and other MAC entities (e.g., SN MAC 1119) for a secondary basestation. In multi-connectivity, a configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and SCGs comprising serving cells of asecondary base station. For an SCG, one or more of followingconfigurations may be used. At least one cell of an SCG may have aconfigured UL CC and at least one cell of a SCG, named as primarysecondary cell (e.g., PSCell, PCell of SCG, PCell), and may beconfigured with PUCCH resources. If an SCG is configured, there may beat least one SCG bearer or one split bearer. After or upon detection ofa physical layer problem or a random access problem on a PSCell, or anumber of NR RLC retransmissions has been reached associated with theSCG, or after or upon detection of an access problem on a PSCellassociated with (e.g., during) a SCG addition or an SCG change: an RRCconnection re-establishment procedure may not be triggered, ULtransmissions towards cells of an SCG may be stopped, a master basestation may be informed by a wireless device of a SCG failure type, a DLdata transfer over a master base station may be maintained (e.g., for asplit bearer). An NR RLC acknowledged mode (AM) bearer may be configuredfor a split bearer. A PCell and/or a PSCell may not be de-activated. APSCell may be changed with a SCG change procedure (e.g., with securitykey change and a RACH procedure). A bearer type change between a splitbearer and a SCG bearer, and/or simultaneous configuration of a SCG anda split bearer, may or may not be supported.

With respect to interactions between a master base station and asecondary base stations for multi-connectivity, one or more of thefollowing may be used. A master base station and/or a secondary basestation may maintain Radio Resource Management (RRM) measurementconfigurations of a wireless device. A master base station may determine(e.g., based on received measurement reports, traffic conditions, and/orbearer types) to request a secondary base station to provide additionalresources (e.g., serving cells) for a wireless device. After or uponreceiving a request from a master base station, a secondary base stationmay create and/or modify a container that may result in a configurationof additional serving cells for a wireless device (or decide that thesecondary base station has no resource available to do so). For awireless device capability coordination, a master base station mayprovide (e.g., all or a part of) an AS configuration and wireless devicecapabilities to a secondary base station. A master base station and asecondary base station may exchange information about a wireless deviceconfiguration such as by using RRC containers (e.g., inter-nodemessages) carried via Xn messages. A secondary base station may initiatea reconfiguration of the secondary base station existing serving cells(e.g., PUCCH towards the secondary base station). A secondary basestation may decide which cell is a PSCell within a SCG. A master basestation may or may not change content of RRC configurations provided bya secondary base station. A master base station may provide recent(and/or the latest) measurement results for SCG cell(s), for example, ifan SCG addition and/or an SCG SCell addition occurs. A master basestation and secondary base stations may receive information of SFNand/or subframe offset of each other from an OAM and/or via an Xninterface (e.g., for a purpose of DRX alignment and/or identification ofa measurement gap). Dedicated RRC signaling may be used for sendingrequired system information of a cell as for CA, for example, if addinga new SCG SCell, except for an SFN acquired from an MIB of a PSCell of aSCG.

FIG. 12 shows an example of a random access procedure. One or moreevents may trigger a random access procedure. For example, one or moreevents may be at least one of following: initial access from RRC_IDLE,RRC connection re-establishment procedure, handover, DL or UL dataarrival in (e.g., during) a state of RRC_CONNECTED (e.g., if ULsynchronization status is non-synchronized), transition fromRRC_Inactive, and/or request for other system information. A PDCCHorder, a MAC entity, and/or a beam failure indication may initiate arandom access procedure.

A random access procedure may comprise or be one of at least acontention based random access procedure and/or a contention free randomaccess procedure. A contention based random access procedure maycomprise one or more Msg 1 1220 transmissions, one or more Msg2 1230transmissions, one or more Msg3 1240 transmissions, and contentionresolution 1250. A contention free random access procedure may compriseone or more Msg 1 1220 transmissions and one or more Msg2 1230transmissions. One or more of Msg 1 1220, Msg 2 1230, Msg 3 1240, and/orcontention resolution 1250 may be transmitted in the same step. Atwo-step random access procedure, for example, may comprise a firsttransmission (e.g., Msg A) and a second transmission (e.g., Msg B). Thefirst transmission (e.g., Msg A) may comprise transmitting, by awireless device (e.g., wireless device 110) to a base station (e.g.,base station 120), one or more messages indicating an equivalent and/orsimilar contents of Msg1 1220 and Msg3 1240 of a four-step random accessprocedure. The second transmission (e.g., Msg B) may comprisetransmitting, by the base station (e.g., base station 120) to a wirelessdevice (e.g., wireless device 110) after or in response to the firstmessage, one or more messages indicating an equivalent and/or similarcontent of Msg2 1230 and contention resolution 1250 of a four-steprandom access procedure.

A base station may send (e.g., transmit, unicast, multicast, broadcast,etc.), to a wireless device, a RACH configuration 1210 via one or morebeams. The RACH configuration 1210 may comprise one or more parametersindicating at least one of following: an available set of PRACHresources for a transmission of a random access preamble, initialpreamble power (e.g., random access preamble initial received targetpower), an RSRP threshold for a selection of a SS block andcorresponding PRACH resource, a power-ramping factor (e.g., randomaccess preamble power ramping step), a random access preamble index, amaximum number of preamble transmissions, preamble group A and group B,a threshold (e.g., message size) to determine the groups of randomaccess preambles, a set of one or more random access preambles for asystem information request and corresponding PRACH resource(s) (e.g., ifany), a set of one or more random access preambles for a beam failurerecovery procedure and corresponding PRACH resource(s) (e.g., if any), atime window to monitor RA response(s), a time window to monitorresponse(s) on a beam failure recovery procedure, and/or a contentionresolution timer.

The Msg1 1220 may comprise one or more transmissions of a random accesspreamble. For a contention based random access procedure, a wirelessdevice may select an SS block with an RSRP above the RSRP threshold. Ifrandom access preambles group B exists, a wireless device may select oneor more random access preambles from a group A or a group B, forexample, depending on a potential Msg3 1240 size. If a random accesspreambles group B does not exist, a wireless device may select the oneor more random access preambles from a group A. A wireless device mayselect a random access preamble index randomly (e.g., with equalprobability or a normal distribution) from one or more random accesspreambles associated with a selected group. If a base stationsemi-statically configures a wireless device with an association betweenrandom access preambles and SS blocks, the wireless device may select arandom access preamble index randomly with equal probability from one ormore random access preambles associated with a selected SS block and aselected group.

A wireless device may initiate a contention free random accessprocedure, for example, based on a beam failure indication from a lowerlayer. A base station may semi-statically configure a wireless devicewith one or more contention free PRACH resources for a beam failurerecovery procedure associated with at least one of SS blocks and/orCSI-RSs. A wireless device may select a random access preamble indexcorresponding to a selected SS block or a CSI-RS from a set of one ormore random access preambles for a beam failure recovery procedure, forexample, if at least one of the SS blocks with an RSRP above a firstRSRP threshold amongst associated SS blocks is available, and/or if atleast one of CSI-RSs with a RSRP above a second RSRP threshold amongstassociated CSI-RSs is available.

A wireless device may receive, from a base station, a random accesspreamble index via PDCCH or RRC for a contention free random accessprocedure. The wireless device may select a random access preambleindex, for example, if a base station does not configure a wirelessdevice with at least one contention free PRACH resource associated withSS blocks or CSI-RS. The wireless device may select the at least one SSblock and/or select a random access preamble corresponding to the atleast one SS block, for example, if a base station configures thewireless device with one or more contention free PRACH resourcesassociated with SS blocks and/or if at least one SS block with a RSRPabove a first RSRP threshold amongst associated SS blocks is available.The wireless device may select the at least one CSI-RS and/or select arandom access preamble corresponding to the at least one CSI-RS, forexample, if a base station configures a wireless device with one or morecontention free PRACH resources associated with CSI-RSs and/or if atleast one CSI-RS with a RSRP above a second RSPR threshold amongst theassociated CSI-RSs is available.

A wireless device may perform one or more Msg1 1220 transmissions, forexample, by sending (e.g., transmitting) the selected random accesspreamble. The wireless device may determine a PRACH occasion from one ormore PRACH occasions corresponding to a selected SS block, for example,if the wireless device selects an SS block and is configured with anassociation between one or more PRACH occasions and/or one or more SSblocks. The wireless device may determine a PRACH occasion from one ormore PRACH occasions corresponding to a selected CSI-RS, for example, ifthe wireless device selects a CSI-RS and is configured with anassociation between one or more PRACH occasions and one or more CSI-RSs.The wireless device may send (e.g., transmit), to a base station, aselected random access preamble via a selected PRACH occasions. Thewireless device may determine a transmit power for a transmission of aselected random access preamble at least based on an initial preamblepower and a power-ramping factor. The wireless device may determine anRA-RNTI associated with a selected PRACH occasion in which a selectedrandom access preamble is sent (e.g., transmitted). The wireless devicemay not determine an RA-RNTI for a beam failure recovery procedure. Thewireless device may determine an RA-RNTI at least based on an index of afirst OFDM symbol, an index of a first slot of a selected PRACHoccasions, and/or an uplink carrier index for a transmission of Msg11220.

A wireless device may receive, from a base station, a random accessresponse, Msg 2 1230. The wireless device may start a time window (e.g.,ra-ResponseWindow) to monitor a random access response. For a beamfailure recovery procedure, the base station may configure the wirelessdevice with a different time window (e.g., bfr-ResponseWindow) tomonitor response to on a beam failure recovery request. The wirelessdevice may start a time window (e.g., ra-ResponseWindow orbfr-ResponseWindow) at a start of a first PDCCH occasion, for example,after a fixed duration of one or more symbols from an end of a preambletransmission. If the wireless device sends (e.g., transmits) multiplepreambles, the wireless device may start a time window at a start of afirst PDCCH occasion after a fixed duration of one or more symbols froman end of a first preamble transmission. The wireless device may monitora PDCCH of a cell for at least one random access response identified bya RA-RNTI, or for at least one response to a beam failure recoveryrequest identified by a C-RNTI, at a time that a timer for a time windowis running.

A wireless device may determine that a reception of random accessresponse is successful, for example, if at least one random accessresponse comprises a random access preamble identifier corresponding toa random access preamble sent (e.g., transmitted) by the wirelessdevice. The wireless device may determine that the contention freerandom access procedure is successfully completed, for example, if areception of a random access response is successful. The wireless devicemay determine that a contention free random access procedure issuccessfully complete, for example, if a contention free random accessprocedure is triggered for a beam failure recovery request and if aPDCCH transmission is addressed to a C-RNTI. The wireless device maydetermine that the random access procedure is successfully completed,and may indicate a reception of an acknowledgement for a systeminformation request to upper layers, for example, if at least one randomaccess response comprises a random access preamble identifier. Thewireless device may stop sending (e.g., transmitting) remainingpreambles (if any) after or in response to a successful reception of acorresponding random access response, for example, if the wirelessdevice has signaled multiple preamble transmissions.

The wireless device may perform one or more Msg 3 1240 transmissions,for example, after or in response to a successful reception of randomaccess response (e.g., for a contention based random access procedure).The wireless device may adjust an uplink transmission timing, forexample, based on a timing advanced command indicated by a random accessresponse. The wireless device may send (e.g., transmit) one or moretransport blocks, for example, based on an uplink grant indicated by arandom access response. Subcarrier spacing for PUSCH transmission forMsg3 1240 may be provided by at least one higher layer (e.g., RRC)parameter. The wireless device may send (e.g., transmit) a random accesspreamble via a PRACH, and Msg3 1240 via PUSCH, on the same cell. A basestation may indicate an UL BWP for a PUSCH transmission of Msg3 1240 viasystem information block. The wireless device may use HARQ for aretransmission of Msg 3 1240.

Multiple wireless devices may perform Msg 1 1220, for example, bysending (e.g., transmitting) the same preamble to a base station. Themultiple wireless devices may receive, from the base station, the samerandom access response comprising an identity (e.g., TC-RNTI).Contention resolution (e.g., comprising the wireless device 110receiving contention resolution 1250) may be used to increase thelikelihood that a wireless device does not incorrectly use an identityof another wireless device. The contention resolution 1250 may be basedon, for example, a C-RNTI on a PDCCH, and/or a wireless devicecontention resolution identity on a DL-SCH. If a base station assigns aC-RNTI to a wireless device, the wireless device may perform contentionresolution (e.g., comprising receiving contention resolution 1250), forexample, based on a reception of a PDCCH transmission that is addressedto the C-RNTI. The wireless device may determine that contentionresolution is successful, and/or that a random access procedure issuccessfully completed, for example, after or in response to detecting aC-RNTI on a PDCCH. If a wireless device has no valid C-RNTI, acontention resolution may be addressed by using a TC-RNTI. If a MAC PDUis successfully decoded and a MAC PDU comprises a wireless devicecontention resolution identity MAC CE that matches or otherwisecorresponds with the CCCH SDU sent (e.g., transmitted) in Msg3 1240, thewireless device may determine that the contention resolution (e.g.,comprising contention resolution 1240) is successful and/or the wirelessdevice may determine that the random access procedure is successfullycompleted.

FIG. 13 shows an example structure for MAC entities. A wireless devicemay be configured to operate in a multi-connectivity mode. A wirelessdevice in RRC_CONNECTED with multiple Rx/Tx may be configured to utilizeradio resources provided by multiple schedulers that may be located in aplurality of base stations. The plurality of base stations may beconnected via a non-ideal or ideal backhaul over the Xn interface. Abase station in a plurality of base stations may act as a master basestation or as a secondary base station. A wireless device may beconnected to and/or in communication with, for example, one master basestation and one or more secondary base stations. A wireless device maybe configured with multiple MAC entities, for example, one MAC entityfor a master base station, and one or more other MAC entities forsecondary base station(s). A configured set of serving cells for awireless device may comprise two subsets: an MCG comprising servingcells of a master base station, and one or more SCGs comprising servingcells of a secondary base station(s). FIG. 13 shows an example structurefor MAC entities in which a MCG and a SCG are configured for a wirelessdevice.

At least one cell in a SCG may have a configured UL CC. A cell of the atleast one cell may comprise a PSCell or a PCell of a SCG, or a PCell. APSCell may be configured with PUCCH resources. There may be at least oneSCG bearer, or one split bearer, for a SCG that is configured. After orupon detection of a physical layer problem or a random access problem ona PSCell, after or upon reaching a number of RLC retransmissionsassociated with the SCG, and/or after or upon detection of an accessproblem on a PSCell associated with (e.g., during) a SCG addition or aSCG change: an RRC connection re-establishment procedure may not betriggered, UL transmissions towards cells of a SCG may be stopped,and/or a master base station may be informed by a wireless device of aSCG failure type and DL data transfer over a master base station may bemaintained.

A MAC sublayer may provide services such as data transfer and radioresource allocation to upper layers (e.g., 1310 or 1320). A MAC sublayermay comprise a plurality of MAC entities (e.g., 1350 and 1360). A MACsublayer may provide data transfer services on logical channels. Toaccommodate different kinds of data transfer services, multiple types oflogical channels may be defined. A logical channel may support transferof a particular type of information. A logical channel type may bedefined by what type of information (e.g., control or data) istransferred. BCCH, PCCH, CCCH and/or DCCH may be control channels, andDTCH may be a traffic channel. A first MAC entity (e.g., 1310) mayprovide services on PCCH, BCCH, CCCH, DCCH, DTCH, and/or MAC controlelements. A second MAC entity (e.g., 1320) may provide services on BCCH,DCCH, DTCH, and/or MAC control elements.

A MAC sublayer may expect from a physical layer (e.g., 1330 or 1340)services such as data transfer services, signaling of HARQ feedback,and/or signaling of scheduling request or measurements (e.g., CQI). Indual connectivity, two MAC entities may be configured for a wirelessdevice: one for a MCG and one for a SCG. A MAC entity of a wirelessdevice may handle a plurality of transport channels. A first MAC entitymay handle first transport channels comprising a PCCH of a MCG, a firstBCH of the MCG, one or more first DL-SCHs of the MCG, one or more firstUL-SCHs of the MCG, and/or one or more first RACHs of the MCG. A secondMAC entity may handle second transport channels comprising a second BCHof a SCG, one or more second DL-SCHs of the SCG, one or more secondUL-SCHs of the SCG, and/or one or more second RACHs of the SCG.

If a MAC entity is configured with one or more SCells, there may bemultiple DL-SCHs, multiple UL-SCHs, and/or multiple RACHs per MACentity. There may be one DL-SCH and/or one UL-SCH on an SpCell. Theremay be one DL-SCH, zero or one UL-SCH, and/or zero or one RACH for anSCell. A DL-SCH may support receptions using different numerologiesand/or TTI duration within a MAC entity. A UL-SCH may supporttransmissions using different numerologies and/or TTI duration withinthe MAC entity.

A MAC sublayer may support different functions. The MAC sublayer maycontrol these functions with a control (e.g., Control 1355 and/orControl 1365) element. Functions performed by a MAC entity may compriseone or more of: mapping between logical channels and transport channels(e.g., in uplink or downlink), multiplexing (e.g., (De-) Multiplexing1352 and/or (De-) Multiplexing 1362) of MAC SDUs from one or differentlogical channels onto transport blocks (TBs) to be delivered to thephysical layer on transport channels (e.g., in uplink), demultiplexing(e.g., (De-) Multiplexing 1352 and/or (De-) Multiplexing 1362) of MACSDUs to one or different logical channels from transport blocks (TBs)delivered from the physical layer on transport channels (e.g., indownlink), scheduling information reporting (e.g., in uplink), errorcorrection through HARQ in uplink and/or downlink (e.g., 1363), andlogical channel prioritization in uplink (e.g., Logical ChannelPrioritization 1351 and/or Logical Channel Prioritization 1361). A MACentity may handle a random access process (e.g., Random Access Control1354 and/or Random Access Control 1364).

FIG. 14 shows an example of a RAN architecture comprising one or morebase stations. A protocol stack (e.g., RRC, SDAP, PDCP, RLC, MAC, and/orPHY) may be supported at a node. A base station (e.g., gNB 120A and/or120B) may comprise a base station central unit (CU) (e.g., gNB-CU 1420Aor 1420B) and at least one base station distributed unit (DU) (e.g.,gNB-DU 1430A, 1430B, 1430C, and/or 1430D), for example, if a functionalsplit is configured. Upper protocol layers of a base station may belocated in a base station CU, and lower layers of the base station maybe located in the base station DUs. An F1 interface (e.g., CU-DUinterface) connecting a base station CU and base station DUs may be anideal or non-ideal backhaul. F1-C may provide a control plane connectionover an F1 interface, and F1-U may provide a user plane connection overthe F1 interface. An Xn interface may be configured between base stationCUs.

A base station CU may comprise an RRC function, an SDAP layer, and/or aPDCP layer. Base station DUs may comprise an RLC layer, a MAC layer,and/or a PHY layer. Various functional split options between a basestation CU and base station DUs may be possible, for example, bylocating different combinations of upper protocol layers (e.g., RANfunctions) in a base station CU and different combinations of lowerprotocol layers (e.g., RAN functions) in base station DUs. A functionalsplit may support flexibility to move protocol layers between a basestation CU and base station DUs, for example, depending on servicerequirements and/or network environments.

Functional split options may be configured per base station, per basestation CU, per base station DU, per wireless device, per bearer, perslice, and/or with other granularities. In a per base station CU split,a base station CU may have a fixed split option, and base station DUsmay be configured to match a split option of a base station CU. In a perbase station DU split, a base station DU may be configured with adifferent split option, and a base station CU may provide differentsplit options for different base station DUs. In a per wireless devicesplit, a base station (e.g., a base station CU and at least one basestation DUs) may provide different split options for different wirelessdevices. In a per bearer split, different split options may be utilizedfor different bearers. In a per slice splice, different split optionsmay be used for different slices.

FIG. 15 shows example RRC state transitions of a wireless device. Awireless device may be in at least one RRC state among an RRC connectedstate (e.g., RRC Connected 1530, RRC_Connected, etc.), an RRC idle state(e.g., RRC Idle 1510, RRC_Idle, etc.), and/or an RRC inactive state(e.g., RRC Inactive 1520, RRC_Inactive, etc.). In an RRC connectedstate, a wireless device may have at least one RRC connection with atleast one base station (e.g., gNB and/or eNB), which may have a contextof the wireless device (e.g., UE context). A wireless device context(e.g., UE context) may comprise at least one of an access stratumcontext, one or more radio link configuration parameters, bearer (e.g.,data radio bearer (DRB), signaling radio bearer (SRB), logical channel,QoS flow, PDU session, and/or the like) configuration information,security information, PHY/MAC/RLC/PDCP/SDAP layer configurationinformation, and/or the like configuration information for a wirelessdevice. In an RRC idle state, a wireless device may not have an RRCconnection with a base station, and a context of the wireless device maynot be stored in a base station. In an RRC inactive state, a wirelessdevice may not have an RRC connection with a base station. A context ofa wireless device may be stored in a base station, which may comprise ananchor base station (e.g., a last serving base station).

A wireless device may transition an RRC state (e.g., UE RRC state)between an RRC idle state and an RRC connected state in both ways (e.g.,connection release 1540 or connection establishment 1550; and/orconnection reestablishment) and/or between an RRC inactive state and anRRC connected state in both ways (e.g., connection inactivation 1570 orconnection resume 1580). A wireless device may transition its RRC statefrom an RRC inactive state to an RRC idle state (e.g., connectionrelease 1560).

An anchor base station may be a base station that may keep a context ofa wireless device (e.g., UE context) at least at (e.g., during) a timeperiod that the wireless device stays in a RAN notification area (RNA)of an anchor base station, and/or at (e.g., during) a time period thatthe wireless device stays in an RRC inactive state. An anchor basestation may comprise a base station that a wireless device in an RRCinactive state was most recently connected to in a latest RRC connectedstate, and/or a base station in which a wireless device most recentlyperformed an RNA update procedure. An RNA may comprise one or more cellsoperated by one or more base stations. A base station may belong to oneor more RNAs. A cell may belong to one or more RNAs.

A wireless device may transition, in a base station, an RRC state (e.g.,UE RRC state) from an RRC connected state to an RRC inactive state. Thewireless device may receive RNA information from the base station. RNAinformation may comprise at least one of an RNA identifier, one or morecell identifiers of one or more cells of an RNA, a base stationidentifier, an IP address of the base station, an AS context identifierof the wireless device, a resume identifier, and/or the like.

An anchor base station may broadcast a message (e.g., RAN pagingmessage) to base stations of an RNA to reach to a wireless device in anRRC inactive state. The base stations receiving the message from theanchor base station may broadcast and/or multicast another message(e.g., paging message) to wireless devices in their coverage area, cellcoverage area, and/or beam coverage area associated with the RNA via anair interface.

A wireless device may perform an RNA update (RNAU) procedure, forexample, if the wireless device is in an RRC inactive state and movesinto a new RNA. The RNAU procedure may comprise a random accessprocedure by the wireless device and/or a context retrieve procedure(e.g., UE context retrieve). A context retrieve procedure may comprise:receiving, by a base station from a wireless device, a random accesspreamble; and requesting and/or receiving (e.g., fetching), by a basestation, a context of the wireless device (e.g., UE context) from an oldanchor base station. The requesting and/or receiving (e.g., fetching)may comprise: sending a retrieve context request message (e.g., UEcontext request message) comprising a resume identifier to the oldanchor base station and receiving a retrieve context response messagecomprising the context of the wireless device from the old anchor basestation.

A wireless device in an RRC inactive state may select a cell to camp onbased on at least a measurement result for one or more cells, a cell inwhich a wireless device may monitor an RNA paging message, and/or a corenetwork paging message from a base station. A wireless device in an RRCinactive state may select a cell to perform a random access procedure toresume an RRC connection and/or to send (e.g., transmit) one or morepackets to a base station (e.g., to a network). The wireless device mayinitiate a random access procedure to perform an RNA update procedure,for example, if a cell selected belongs to a different RNA from an RNAfor the wireless device in an RRC inactive state. The wireless devicemay initiate a random access procedure to send (e.g., transmit) one ormore packets to a base station of a cell that the wireless deviceselects, for example, if the wireless device is in an RRC inactive stateand has one or more packets (e.g., in a buffer) to send (e.g., transmit)to a network. A random access procedure may be performed with twomessages (e.g., 2-stage or 2-step random access) and/or four messages(e.g., 4-stage or 4-step random access) between the wireless device andthe base station.

A base station receiving one or more uplink packets from a wirelessdevice in an RRC inactive state may request and/or receive (e.g., fetch)a context of a wireless device (e.g., UE context), for example, bysending (e.g., transmitting) a retrieve context request message for thewireless device to an anchor base station of the wireless device basedon at least one of an AS context identifier, an RNA identifier, a basestation identifier, a resume identifier, and/or a cell identifierreceived from the wireless device. A base station may send (e.g.,transmit) a path switch request for a wireless device to a core networkentity (e.g., AMF, MME, and/or the like), for example, after or inresponse to requesting and/or receiving (e.g., fetching) a context. Acore network entity may update a downlink tunnel endpoint identifier forone or more bearers established for the wireless device between a userplane core network entity (e.g., UPF, S-GW, and/or the like) and a RANnode (e.g., the base station), such as by changing a downlink tunnelendpoint identifier from an address of the anchor base station to anaddress of the base station).

A base station may communicate with a wireless device via a wirelessnetwork using one or more technologies, such as new radio technologies(e.g., NR, 5G, etc.). The one or more radio technologies may comprise atleast one of: multiple technologies related to physical layer; multipletechnologies related to medium access control layer; and/or multipletechnologies related to radio resource control layer Enhancing the oneor more radio technologies may improve performance of a wirelessnetwork. System throughput, and/or data rate of transmission, may beincreased. Battery consumption of a wireless device may be reduced.Latency of data transmission between a base station and a wirelessdevice may be improved. Network coverage of a wireless network may beimproved. Transmission efficiency of a wireless network may be improved.

A base station may send (e.g., transmit) one or more MAC PDUs to awireless device. A MAC PDU may comprise a bit string that may be bytealigned (e.g., multiple of eight bits) in length. Bit strings may berepresented by tables in which the most significant bit is the leftmostbit of the first line of the table, and the least significant bit is therightmost bit on the last line of the table. The bit string may be readfrom the left to right, and then, in the reading order of the lines. Thebit order of a parameter field within a MAC PDU may be represented withthe first and most significant bit in the leftmost bit, and with thelast and least significant bit in the rightmost bit.

A MAC SDU may comprise a bit string that is byte aligned (e.g., multipleof eight bits) in length. A MAC SDU may be included in a MAC PDU, forexample, from the first bit onward. In an example, a MAC CE may be a bitstring that is byte aligned (e.g., multiple of eight bits) in length. AMAC subheader may be a bit string that is byte aligned (e.g., multipleof eight bits) in length. A MAC subheader may be placed immediately infront of the corresponding MAC SDU, MAC CE, and/or padding. A MAC entitymay ignore a value of reserved bits in a DL MAC PDU.

A MAC PDU may comprise one or more MAC subPDUs. A MAC subPDU of the oneor more MAC subPDUs may comprise at least one of: a MAC subheader only(e.g., including padding); a MAC subheader and a MAC SDU; a MACsubheader and a MAC CE; and/or a MAC subheader and padding. The MAC SDUmay be of variable size. A MAC subheader may correspond to a MAC SDU, aMAC CE, and/or padding.

A MAC subheader may comprise: an R field comprising one bit; an F fieldwith one bit in length; an LCID field with multiple bits in length;and/or an L field with multiple bits in length. The MAC subheader maycorrespond to a MAC SDU, a variable-sized MAC CE, and/or padding.

FIG. 16A shows an example of a MAC subheader comprising an eight-bit Lfield. The LCID field may have six bits in length (or any other quantityof bits). The L field may have eight bits in length (or any otherquantity of bits).

FIG. 16B shows an example of a MAC subheader with a sixteen-bit L field.The LCID field may have six bits in length (or any other quantity ofbits). The L field may have sixteen bits in length (or any otherquantity of bits). A MAC subheader may comprise: a R field comprisingtwo bits in length (or any other quantity of bits); and an LCID fieldcomprising multiple bits in length (e.g., if the MAC subheadercorresponds to a fixed sized MAC CE), and/or padding.

FIG. 16C shows an example of the MAC subheader. The LCID field maycomprise six bits in length (or any other quantity of bits). The R fieldmay comprise two bits in length (or any other quantity of bits).

FIG. 17A shows an example of a DL MAC PDU. Multiple MAC CEs may beplaced together. A MAC subPDU comprising MAC CE may be placed before anyMAC subPDU comprising a MAC SDU, and/or before a MAC subPDU comprisingpadding.

FIG. 17B shows an example of a UL MAC PDU. Multiple MAC CEs may beplaced together. A MAC subPDU comprising a MAC CE may be placed afterall MAC subPDU comprising a MAC SDU. The MAC subPDU may be placed beforea MAC subPDU comprising padding.

FIG. 18 shows first examples of LCIDs. FIG. 19 shows second examples ofLCIDs. In each of FIG. 18 and FIG. 19 , the left columns compriseindices, and the right columns comprises corresponding LCID values foreach index.

FIG. 18 shows an example of an LCID that may be associated with the oneor more MAC CEs. A MAC entity of a base station may send (e.g.,transmit) to a MAC entity of a wireless device one or more MAC CEs. Theone or more MAC CEs may comprise at least one of: an SP ZP CSI-RSResource Set Activation/Deactivation MAC CE; a PUCCH spatial relationActivation/Deactivation MAC CE; a SP SRS Activation/Deactivation MAC CE;a SP CSI reporting on PUCCH Activation/Deactivation MAC CE; a TCI StateIndication for UE-specific PDCCH MAC CE; a TCI State Indication forUE-specific PDSCH MAC CE; an Aperiodic CSI Trigger State SubselectionMAC CE; a SP CSI-RS/CSI-IM Resource Set Activation/Deactivation MAC CE;a wireless device (e.g., UE) contention resolution identity MAC CE; atiming advance command MAC CE; a DRX command MAC CE; a long DRX commandMAC CE; an SCell activation and/or deactivation MAC CE (e.g., 1 Octet);an SCell activation and/or deactivation MAC CE (e.g., 4 Octet); and/or aduplication activation and/or deactivation MAC CE. A MAC CE may comprisean LCID in the corresponding MAC subheader. Different MAC CEs may havedifferent LCID in the corresponding MAC subheader. An LCID with 111011in a MAC subheader may indicate that a MAC CE associated with the MACsubheader is a long DRX command MAC CE.

FIG. 19 shows further examples of LCIDs associated with one or more MACCEs. The MAC entity of the wireless device may send (e.g., transmit), tothe MAC entity of the base station, one or more MAC CEs. The one or moreMAC CEs may comprise at least one of: a short buffer status report (BSR)MAC CE; a long BSR MAC CE; a C-RNTI MAC CE; a configured grantconfirmation MAC CE; a single entry power headroom report (PHR) MAC CE;a multiple entry PHR MAC CE; a short truncated BSR; and/or a longtruncated BSR. A MAC CE may comprise an LCID in the corresponding MACsubheader. Different MAC CEs may have different LCIDs in thecorresponding MAC subheader. The LCID with 111011 in a MAC subheader mayindicate that a MAC CE associated with the MAC subheader is ashort-truncated command MAC CE.

Two or more component carriers (CCs) may be aggregated, for example, ina carrier aggregation (CA). A wireless device may simultaneously receiveand/or transmit on one or more CCs, for example, depending oncapabilities of the wireless device. The CA may be supported forcontiguous CCs. The CA may be supported for non-contiguous CCs.

A wireless device may have one RRC connection with a network, forexample, if configured with CA. At (e.g., during) an RRC connectionestablishment, re-establishment and/or handover, a cell providing a NASmobility information may be a serving cell. At (e.g., during) an RRCconnection re-establishment and/or handover procedure, a cell providinga security input may be a serving cell. The serving cell may be referredto as a primary cell (PCell). A base station may send (e.g., transmit),to a wireless device, one or more messages comprising configurationparameters of a plurality of one or more secondary cells (SCells), forexample, depending on capabilities of the wireless device.

A base station and/or a wireless device may use an activation and/ordeactivation mechanism of an SCell for an efficient battery consumption,for example, if the base station and/or the wireless device isconfigured with CA. A base station may activate or deactivate at leastone of the one or more SCells, for example, if the wireless device isconfigured with one or more SCells. The SCell may be deactivated, forexample, after or upon configuration of an SCell.

A wireless device may activate and/or deactivate an SCell, for example,after or in response to receiving an SCell activation and/ordeactivation MAC CE. A base station may send (e.g., transmit), to awireless device, one or more messages comprising ansCellDeactivationTimer timer. The wireless device may deactivate anSCell, for example, after or in response to an expiry of thesCellDeactivationTimer timer.

A wireless device may activate an SCell, for example, if the wirelessdevice receives an SCell activation/deactivation MAC CE activating anSCell. The wireless device may perform operations (e.g., after or inresponse to the activating the SCell) that may comprise: SRStransmissions on the SCell; CQI, PMI, RI, and/or CRI reporting for theSCell on a PCell; PDCCH monitoring on the SCell; PDCCH monitoring forthe SCell on the PCell; and/or PUCCH transmissions on the SCell.

The wireless device may start and/or restart a timer (e.g., ansCellDeactivationTimer timer) associated with the SCell, for example,after or in response to activating the SCell. The wireless device maystart the timer (e.g., sCellDeactivationTimer timer) in the slot, forexample, if the SCell activation/deactivation MAC CE has been received.The wireless device may initialize and/or re-initialize one or moresuspended configured uplink grants of a configured grant Type 1associated with the SCell according to a stored configuration, forexample, after or in response to activating the SCell. The wirelessdevice may trigger a PHR, for example, after or in response toactivating the SCell.

The wireless device may deactivate the activated SCell, for example, ifthe wireless device receives an SCell activation/deactivation MAC CEdeactivating an activated SCell. The wireless device may deactivate theactivated SCell, for example, if a timer (e.g., ansCellDeactivationTimer timer) associated with an activated SCellexpires. The wireless device may stop the timer (e.g.,sCellDeactivationTimer timer) associated with the activated SCell, forexample, after or in response to deactivating the activated SCell. Thewireless device may clear one or more configured downlink assignmentsand/or one or more configured uplink grant Type 2 associated with theactivated SCell, for example, after or in response to the deactivatingthe activated SCell. The wireless device may suspend one or moreconfigured uplink grant Type 1 associated with the activated SCell,and/or flush HARQ buffers associated with the activated SCell, forexample, after or in response to deactivating the activated SCell.

A wireless device may refrain from performing certain operations, forexample, if an SCell is deactivated. The wireless device may refrainfrom performing one or more of the following operations if an SCell isdeactivated: transmitting SRS on the SCell; reporting CQI, PMI, RI,and/or CRI for the SCell on a PCell; transmitting on UL-SCH on theSCell; transmitting on a RACH on the SCell; monitoring at least onefirst PDCCH on the SCell; monitoring at least one second PDCCH for theSCell on the PCell; and/or transmitting a PUCCH on the SCell.

A wireless device may restart a timer (e.g., an sCellDeactivationTimertimer) associated with the activated SCell, for example, if at least onefirst PDCCH on an activated SCell indicates an uplink grant or adownlink assignment. A wireless device may restart a timer (e.g., ansCellDeactivationTimer timer) associated with the activated SCell, forexample, if at least one second PDCCH on a serving cell (e.g. a PCell oran SCell configured with PUCCH, such as a PUCCH SCell) scheduling theactivated SCell indicates an uplink grant and/or a downlink assignmentfor the activated SCell. A wireless device may abort the ongoing randomaccess procedure on the SCell, for example, if an SCell is deactivatedand/or if there is an ongoing random access procedure on the SCell.

FIG. 20A shows an example of an SCell activation/deactivation MAC CEthat may comprise one octet. A first MAC PDU subheader comprising afirst LCID (e.g., LCID 111010) may indicate/identify the SCellactivation/deactivation MAC CE of one octet. An SCellactivation/deactivation MAC CE of one octet may have a fixed size. TheSCell activation/deactivation MAC CE of one octet may comprise a singleoctet. The single octet may comprise a first number of C-fields (e.g.,seven) and a second number of R-fields (e.g., one).

FIG. 20B shows an example of an SCell Activation/Deactivation MAC CE offour octets. A second MAC PDU subheader with a second LCID (e.g., LCID111001) may indicate/identify the SCell Activation/Deactivation MAC CEof four octets. An SCell activation/deactivation MAC CE of four octetsmay have a fixed size. The SCell activation/deactivation MAC CE of fouroctets may comprise four octets. The four octets may comprise a thirdnumber of C-fields (e.g., 31) and a fourth number of R-fields (e.g., 1).A C_(i) field may indicate an activation/deactivation status of an SCellwith an SCell index i, for example, if an SCell with SCell index i isconfigured. An SCell with an SCell index i may be activated, forexample, if the C_(i) field is set to one. An SCell with an SCell indexi may be deactivated, for example, if the C_(i) field is set to zero.The wireless device may ignore the C_(i) field, for example, if there isno SCell configured with SCell index i. An R field may indicate areserved bit. The R field may be set to zero.

A base station and/or a wireless device may use a power saving mechanism(e.g., hibernation mechanism) for an SCell, for example, if CA isconfigured. A power saving mechanism may improve battery performance(e.g., run-times), reduce power consumption of the wireless device,and/or to improve latency of SCell activation and/or SCell addition. TheSCell may be transitioned (e.g., switched and/or adjusted) to a dormantstate if the wireless device initiates a power saving state for (e.g.,hibernates) the SCell. The wireless device may, for example, if theSCell is transitioned to a dormant state: stop transmitting SRS on theSCell, report CQI/PMI/RI/PTI/CRI for the SCell according to or based ona periodicity configured for the SCell in a dormant state, not transmiton an UL-SCH on the SCell, not transmit on a RACH on the SCell, notmonitor the PDCCH on the SCell, not monitor the PDCCH for the SCell,and/or not transmit PUCCH on the SCell. Not transmitting, notmonitoring, not receiving, and/or not performing an action may comprise,for example, refraining from transmitting, refraining from monitoring,refraining from receiving, and/or refraining from performing an action,respectively. Reporting CSI for an SCell, that has been transitioned toa dormant state, and not monitoring the PDCCH on/for the SCell, mayprovide the base station an “always-updated” CSI for the SCell. The basestation may use a quick and/or accurate channel adaptive scheduling onthe SCell, based on the always-updated CSI, if the SCell is transitionedback to active state. Using the always-updated CSI may speed up anactivation procedure of the SCell. Reporting CSI for the SCell and notmonitoring the PDCCH on and/or for the SCell (e.g., that may have beentransitioned to a dormant state), may provide advantages such asincreased battery efficiency, reduced power consumption of the wirelessdevice, and/or increased timeliness and/or accuracy of channel feedbackinformation feedback. A PCell/PSCell and/or a PUCCH SCell, for example,may not be configured or transitioned to a dormant state.

A base station may activate, hibernate, or deactivate at least one ofone or more configured SCells. A base station may send (e.g., transmit)to a wireless device, for example, one or more messages comprisingparameters indicating at least one SCell being set to an active state, adormant state, or an inactive state.

A base station may transmit, for example, one or more RRC messagescomprising parameters indicating at least one SCell being set to anactive state, a dormant state, or an inactive state. A base station maytransmit, for example, one or more MAC control elements (CEs) comprisingparameters indicating at least one SCell being set to an active state, adormant state, or an inactive state.

The wireless device may perform (e.g., if the SCell is in an activestate): SRS transmissions on the SCell, CQI/PMI/RI/CRI reporting for theSCell, PDCCH monitoring on the SCell, PDCCH monitoring for the SCell,and/or PUCCH/SPUCCH transmissions on the SCell. The wireless device may(e.g., if the SCell is in an inactive state): not transmit SRS on theSCell, not report CQI/PMI/RI/CRI for the SCell, not transmit on anUL-SCH on the SCell, not transmit on a RACH on the SCell, not monitorPDCCH on the SCell, not monitor a PDCCH for the SCell; and/or nottransmit a PUCCH/SPUCCH on the SCell. The wireless device may (e.g., ifthe SCell is in a dormant state): not transmit SRS on the SCell, reportCQI/PMI/RI/CRI for the SCell, not transmit on a UL-SCH on the SCell, nottransmit on a RACH on the SCell, not monitor a PDCCH on the SCell, notmonitor a PDCCH for the SCell, and/or not transmit a PUCCH/SPUCCH on theSCell.

A base station may send (e.g., transmit), for example, a first MAC CE(e.g., an activation/deactivation MAC CE). The first MAC CE mayindicate, to a wireless device, activation or deactivation of at leastone SCell. A C_(i) field may indicate an activation/deactivation statusof an SCell with an SCell index i, for example, if an SCell with SCellindex i is configured. An SCell with an SCell index i may be activated,for example, if the C_(i) field is set to one. An SCell with an SCellindex i may be deactivated, for example, if the C_(i) field is set tozero. A wireless device receiving a MAC CE may ignore the C_(i) field,for example, if there is no SCell configured with SCell index i. An Rfield may indicate a reserved bit. The R field may be set to zero.

A base station may transmit a MAC CE (e.g., a hibernation MAC CE) thatmay generally be referred to herein as a second MAC CE. The second MACCE may be the same as or different from other MAC CEs described herein,but is generally referred to herein as the second MAC CE. The second MACCE may indicate activation and/or hibernation of at least one SCell to awireless device. The second MAC CE may be associated with, for example,a second LCID different from a first LCID of the first MAC CE (e.g., theactivation/deactivation MAC CE). The second MAC CE may have a fixedsize. The second MAC CE may comprise a single octet comprising sevenC-fields and one R-field.

FIG. 21A shows an example of a MAC CE (e.g., the second MAC CEreferenced above) comprising a single octet. The second MAC CE maycomprise four octets comprising 31 C-fields and one R-field. FIG. 21Bshows an example of the second MAC CE comprising four octets. A secondMAC CE (e.g., comprising four octets) may be associated with a thirdLCID. The third LCID may be different from the second LCID for thesecond MAC CE and/or the first LCID for activation/deactivation MAC CE.The second MAC CE (e.g., comprising one octet) may be used, for example,if there is no SCell with a serving cell index greater than a value(e.g., 7 or any other value). The second MAC CE (e.g., comprising fouroctets) may be used, for example, if there is an SCell with a servingcell index greater than a value (e.g., 7 or any other value). A secondMAC CE may indicate a dormant/activated status of an SCell, for example,if a second MAC CE is received and a first MAC CE is not received. TheC_(i) field of the second MAC CE may indicate a dormant/activated statusof an SCell with SCell index i if there is an SCell configured withSCell index i, otherwise the MAC entity may ignore the C_(i) field. Awireless device may transition an SCell associated with SCell index iinto a dormant state, for example, if C_(i) of the second MAC CE is setto “1”. The wireless device may activate an SCell associated with SCellindex i, for example, if C_(i) of the second MAC CE is set to “0”. Thewireless device may activate the SCell with SCell index i, for example,if C_(i) of the second MAC CE is set to “0” and the SCell with SCellindex i is in a dormant state. The wireless device may ignore the C_(i)field of the second MAC CE, for example, if the C_(i) field is set to“0” and the SCell with SCell index i is not in a dormant state.

FIG. 21C shows example configurations of a field of the first MAC CE.The field may comprise, for example, a C_(i) field of the first MAC CE(e.g., an activation/deactivation MAC CE), a C_(i) field of the secondMAC CE (e.g., a hibernation MAC CE), and corresponding resulting SCellstatus (e.g., activated/deactivated/dormant). The wireless device maydeactivate an SCell associated with SCell index i, for example, if C_(i)of hibernation MAC CE is set to 0, and C_(i) of theactivation/deactivation MAC CE is set to 0. The wireless device mayactivate an SCell associated with SCell index i, for example, if C_(i)of hibernation MAC CE is set to 0, and C_(i) of theactivation/deactivation MAC CE is set to 1. The wireless device mayignore the hibernation MAC CE and the activation/deactivation MAC CE,for example, if C_(i) of hibernation MAC CE is set to 1, and C_(i) ofthe activation/deactivation MAC CE is set to 0. The wireless device maytransition an SCell associated with SCell index I to a dormant state,for example, if C_(i) of hibernation MAC CE is set to 1, and C_(i) ofthe activation/deactivation MAC CE is set to 1.

A base station may activate, hibernate, and/or deactivate at least oneof one or more SCells, for example, if the base station is configuredwith the one or more SCells. A MAC entity of a base station and/or awireless device may maintain an SCell deactivation timer (e.g.,sCellDeactivationTimer), for example, per a configured SCell and/orexcept for an SCell configured with PUCCH/SPUCCH, if any. The MAC entityof the base station and/or the wireless device may deactivate anassociated SCell, for example, if an SCell deactivation timer expires. AMAC entity of a base station and/or a wireless device may maintaindormant SCell deactivation timer (e.g., dormantSCellDeactivationTimer),for example, per a configured SCell and/or except for an SCellconfigured with PUCCH/SPUCCH, if any. The MAC entity of the base stationand/or the wireless device may deactivate an associated SCell, forexample, if the dormant SCell deactivation timer expires (e.g., if theSCell is in dormant state).

A base station (e.g., a MAC entity of the base station) and/or awireless device (e.g., a MAC entity of the wireless device) may, forexample, maintain an SCell hibernation timer (e.g.,sCellHibernationTimer), for example, per a configured SCell and/orexcept for an SCell configured with PUCCH/SPUCCH, if any. The basestation (e.g., the MAC entity of the base station) and/or the wirelessdevice (e.g., the MAC entity of the wireless device) may hibernate anassociated SCell, for example, if the SCell hibernation timer expires(e.g., if the SCell is in active state). The SCell hibernation timer maytake priority over the SCell deactivation timer, for example, if boththe SCell deactivation timer and the SCell hibernation timer areconfigured. A base station and/or a wireless device may ignore the SCelldeactivation timer regardless of the SCell deactivation timer expiry,for example, if both the SCell deactivation timer and the SCellhibernation timer are configured.

A wireless device (e.g., MAC entity of a wireless device) may activatean SCell, for example, if the MAC entity is configured with an activatedSCell at SCell configuration. A wireless device (e.g., MAC entity of awireless device) may activate an SCell, for example, if the wirelessdevice receives a MAC CE(s) activating the SCell. The wireless device(e.g., MAC entity of a wireless device) may start or restart an SCelldeactivation timer associated with an SCell, for example, based on or inresponse to activating the SCell. The wireless device (e.g., MAC entityof a wireless device) may start or restart an SCell hibernation timer(e.g., if configured) associated with an SCell, for example, based on orin response to activating the SCell. A wireless device (e.g., MAC entityof a wireless device) may trigger a PHR procedure, for example, based onor in response to activating an SCell.

A wireless device (e.g., MAC entity of a wireless device) and/or a basestation (e.g., a MAC entity of a base station) may (e.g., if a firstPDCCH on an SCell indicates an uplink grant or downlink assignment, or asecond PDCCH on a serving cell scheduling the SCell indicates an uplinkgrant or a downlink assignment for the SCell, or a MAC PDU istransmitted in a configured uplink grant or received in a configureddownlink assignment) restart an SCell deactivation timer associated withan activated SCell and/or restart an SCell hibernation timer (e.g., ifconfigured) associated with the SCell. An ongoing random access (RA)procedure on an SCell may be aborted, for example, if, the SCell isdeactivated.

A wireless device (e.g., MAC entity of a wireless device) and/or a basestation (e.g., a MAC entity of a base station) may (e.g., if configuredwith an SCell associated with an SCell state set to dormant state uponthe SCell configuration, or if receiving MAC CE(s) indicatingtransitioning the SCell to a dormant state): set (e.g., transition) theSCell to a dormant state, transmit one or more CSI reports for theSCell, stop an SCell deactivation timer associated with the SCell, stopan SCell hibernation timer (if configured) associated with the SCell,start or restart a dormant SCell deactivation timer associated with theSCell, and/or flush all HARQ buffers associated with the SCell. Thewireless device (e.g., MAC entity of a wireless device) and/or a basestation (e.g., a MAC entity of a base station) may (e.g., if the SCellhibernation timer associated with the activated SCell expires):hibernate the SCell, stop the SCell deactivation timer associated withthe SCell, stop the SCell hibernation timer associated with the SCell,and/or flush all HARQ buffers associated with the SCell. The wirelessdevice (e.g., MAC entity of a wireless device) and/or a base station(e.g., a MAC entity of a base station) may (e.g., if a dormant SCelldeactivation timer associated with a dormant SCell expires): deactivatethe SCell and/or stop the dormant SCell deactivation timer associatedwith the SCell. Ongoing RA procedure on an SCell may be aborted, forexample, if the SCell is in dormant state.

FIG. 22 shows example DCI formats. The example DCI formats maycorrespond to an operation such as an FDD operation (e.g., 20 MHzbandwidth, or any other bandwidth). The example DCI formats maycorrespond to transmissions involving two transmission antennas (or anyother number of antennas) at the base station. The example DCI formatsmay correspond to transmissions utilizing CA or not utilizing no carrieraggregation. The DCI formats may comprise at least one of: DCI format0_0/0_1 indicating scheduling of PUSCH in a cell; DCI format 1_0/1_1indicating scheduling of PDSCH in a cell; DCI format 2_0 indicating aslot format (e.g., to a group of wireless devices); DCI format 2_1indicating PRB(s) and/or OFDM symbol(s) to a group of wireless devices(e.g., in a scenario where a wireless device may assume no transmissionis intended for the wireless device); DCI format 2_2 indicatingtransmission of TPC commands for PUCCH and PUSCH; and/or DCI format 2_3indicating transmission of a group of TPC commands for SRS transmissionby one or more wireless devices. A base station may transmit DCI, via aPDCCH, for scheduling decisions and/or power-control commands. The DCImay comprise at least one of: downlink scheduling assignments, uplinkscheduling grants, power-control commands. The downlink schedulingassignments may comprise at least one of: PDSCH resource indication,transport format, HARQ information, control information related tomultiple antenna schemes, and/or a command for power control of thePUCCH used for transmission of ACK/NACK (e.g., based on downlinkscheduling assignments). The uplink scheduling grants may comprise atleast one of: PUSCH resource indication, transport format, and HARQrelated information, and/or a power control command of the PUSCH.

The different types of control information correspond to different DCImessage sizes. Supporting spatial multiplexing with non-contiguousallocation of RBs (e.g., in the frequency domain) may require a largerscheduling message, for example, in comparison with an uplink grant thatallows only contiguous allocation of RBs. The DCI may be categorizedinto different DCI formats. A DCI format may correspond to a certainmessage size and may be associated with a particular application/usage.

A wireless device may monitor one or more PDCCH candidates to detect oneor more DCI with one or more DCI format. One or more PDCCH transmissionsmay be transmitted in a common search space or a wirelessdevice-specific search space. A wireless device may monitor PDCCH withonly a limited set of DCI formats, for example, to reduce powerconsumption. A wireless device may not be required to detect DCI, forexample, with DCI format 6 (e.g., as used for an eMTC wireless device),and/or any other DCI format. A wireless device with a capability fordetection of a higher number of DCI formats may have a higher powerconsumption.

The one or more PDCCH candidates that a wireless device monitors may bedefined in terms of PDCCH wireless device-specific search spaces. APDCCH wireless device-specific search space at CCE aggregation level L(e.g., L∈{1, 2, 4, 8}) may be defined by a set of PDCCH candidates forthe CCE aggregation level L. A wireless device may be configured (e.g.,by one or more higher layer parameters), for a DCI format per servingcell, a number of PDCCH candidates per CCE aggregation level L.

A wireless device may monitor one or more PDCCH candidate in controlresource set q based on a periodicity of symbols (e.g., W_(PDCCH,q)symbols) for control resource set q. The periodicity of the symbols forthe control resource set q may be configured, for example, by one ormore higher layer parameters).

Information in the DCI formats used for downlink scheduling may beorganized into different groups. Fields present in DCIs corresponding todifferent DCI formats may be different. The fields may comprise, forexample, at least one of: resource information (e.g., comprising carrierindicator (e.g., 0 or 3 bits, or any other quantity of bits) and/or RBallocation); HARQ process number; MCS, new data indicator (NDI), andredundancy version (RV) (e.g., for a first TB); MCS, NDI and RV (e.g.,for a second TB); MIMO related information; PDSCH resource-elementmapping and QCI; downlink assignment index (DAI); TPC for PUCCH; SRSrequest (e.g., 1 bit, or any other quantity of bits), an indicator fortriggering one-shot SRS transmission; ACK/NACK offset; DCI format 0/1Aindication (e.g., used to differentiate between DCI format 1A and DCIformat 0); and padding (e.g., if necessary). The MIMO relatedinformation may comprise, for example, at least one of: PMI, precodinginformation, transport block swap flag, power offset between PDSCH andreference signal, reference-signal scrambling sequence, number/quantityof layers, and/or antenna ports for transmission.

Information in the DCI formats used for uplink scheduling may beorganized into different groups. Field present in DCIs corresponding todifferent DCI formats may be different. The fields may comprise, forexample, at least one of: resource information (e.g., comprising carrierindicator, resource allocation type, and/or RB allocation); MCS, NDI(for a first TB); MCS, NDI (for a second TB); phase rotation of anuplink DMRS; precoding information; CSI request, an indicator requestingan aperiodic CSI report; SRS request (e.g., 2 bits, or any otherquantity of bits) to trigger aperiodic SRS transmission (e.g., using oneof up to three preconfigured settings); uplink index/DAI; TPC for PUSCH;DCI format 0/1A indication; and padding (e.g., if necessary).

A base station may perform cyclic redundancy check (CRC) scrambling forDCI, for example, before transmitting the DCI via a PDCCH. The basestation may perform CRC scrambling, for example, by bit-wise addition(or Modulo-2 addition, exclusive OR (XOR) operation, or any othermethod) of multiple bits of at least one wireless device identifier(e.g., C-RNTI, CS-RNTI, TPC-CS-RNTI, TPC-PUCCH-RNTI, TPC-PUSCH-RNTI, SPCSI C-RNTI, SRS-TPC-RNTI, INT-RNTI, SFI-RNTI, P-RNTI, SI-RNTI, RA-RNTI,MCS-C-RNTI, and/or any other identifier) with the CRC bits of the DCI.The wireless device may check the CRC bits of the DCI, for example, ifdetecting the DCI. The wireless device may receive the DCI, for example,if the CRC is scrambled by a sequence of bits that is the same as the atleast one wireless device identifier.

A base station may transmit one or more PDCCH in different controlresource sets, for example, to support wide bandwidth operation. A basestation may transmit one or more RRC message comprising configurationparameters of one or more control resource sets. At least one of the oneor more control resource sets may comprise, for example, at least oneof: a first OFDM symbol; a number/quantity of consecutive OFDM symbols;a set of resource blocks; a CCE-to-REG mapping; and/or a REG bundle size(e.g., for interleaved CCE-to-REG mapping).

A base station may configure a wireless device with BWPs (e.g., UL BWPsand/or DL BWPs) to enable BA on a PCell. The base station may configurethe wireless device with at least DL BWP(s) (e.g., there may be no ULBWPs in the UL) to enable BA on an SCell (e.g., if CA is configured). Aninitial active BWP may be a first BWP used for initial access, forexample, for the PCell. A first active BWP may be a second BWPconfigured for the wireless device to operate on the SCell (e.g., uponthe SCell being activated). A base station and/or a wireless device mayindependently switch a DL BWP and an UL BWP, for example, if operatingin a paired spectrum (e.g., FDD). A base station and/or a wirelessdevice may simultaneously switch a DL BWP and an UL BWP, for example, ifoperating in an unpaired spectrum (e.g., TDD).

A base station and/or a wireless device may switch a BWP betweenconfigured BWPs, for example, based on DCI, a BWP inactivity timer,and/or any trigger. A base station and/or a wireless device may switchan active BWP to a default BWP, for example, based on or in response toan expiry of a BWP inactivity timer, if configured, associated with aserving cell. The default BWP may be configured by the network.

One UL BWP for each uplink carrier and/or one DL BWP may be active at atime in an active serving cell, for example, for FDD systems that may beconfigured with BA. One DL/UL BWP pair may be active at a time in anactive serving cell, for example, for TDD systems. Operating on the oneUL BWP and/or the one DL BWP (or the one DL/UL BWP pair) may improvewireless device battery consumption. BWPs other than the one active ULBWP and/or the one active DL BWP that the wireless device may work onmay be deactivated. On or for deactivated BWPs, the wireless device maynot monitor PDCCH and/or may not transmit on a PUCCH, PRACH, and/orUL-SCH.

A serving cell may be configured with any quantity of BWPs (e.g., up tofour, or up to any other quantity of BWPs). There may be, for example,one or any other quantity of active BWPs at any point in time for anactivated serving cell.

BWP switching for a serving cell may be used, for example, to activatean inactive BWP and/or deactivate an active BWP (e.g., at a time t). TheBWP switching may be controlled, for example, by a PDCCH indicating adownlink assignment and/or an uplink grant. The BWP switching may becontrolled, for example, by a BWP inactivity timer (e.g.,bwp-InactivityTimer). The BWP switching may be controlled, for example,by a base station (e.g., a MAC entity of a base station), a wirelessdevice (e.g., a MAC entity of a wireless device), and/or a MAC entity,based on or in response to initiating an RA procedure. One or more BWPsmay be initially active, without receiving a PDCCH indicating a downlinkassignment or an uplink grant, for example, if an SpCell is added and/orif an SCell is activated. The active BWP for a serving cell may beindicated by RRC message and/or PDCCH. A DL BWP may be paired with an ULBWP. BWP switching may be common for both UL and DL, for example, forunpaired spectrum.

FIG. 23 shows an example of BWP switching for an SCell. A base station2405 may send (e.g., transmit) one or more messages, to a wirelessdevice 2410. The one or more messages may be for configuring BWPscorresponding to the SCell 2415. The one or more messages may comprise,for example, one or more RRC messages (e.g., RRC connectionreconfiguration message, and/or RRC connection reestablishment message,and/or RRC connection setup message). The configured BWPs may compriseBWP 0, BWP 1, . . . BWP n. The BWP 0 may be configured as a default BWP.The BWP 1 may be configured as a first active BWP. At time n, the basestation 2405 may send (e.g., transmit) an RRC message and/or a MAC CEfor activating the SCell. At or after time n+k, and based on thereception of the RRC message and/or the MAC CE, the wireless device 2410may activate the SCell and start monitoring a PDCCH on the BWP 1 (e.g.,the first active BWP). At or after time m, the base station 2405 maysend (e.g., transmit) DCI for DL assignment or UL grant on the BWP 1. Ator after time m+1, the wireless device 2410 may receive a packet on theBWP 1 and may start a BWP inactivity timer (e.g., bwp-InactivityTimer).At time s, the BWP inactivity timer may expire. At or after time s+t, aBWP may switch to BWP 0 based on expiration of the BWP inactivity timer.BWP switching may comprise, for example, activating the BWP 0 anddeactivating the BWP 1. At time o, the base station 2405 may send (e.g,transmit) an RRC message and/or a MAC CE for deactivating an SCell. Ator after time o+p, the wireless device 2410 may stop the BWP inactivitytimer and deactivate the SCell 2415.

A wireless device may receive RRC message comprising parameters of aSCell and one or more BWP configuration associated with the SCell. TheRRC message may comprise: RRC connection reconfiguration message (e.g.,RRCReconfiguration); RRC connection reestablishment message (e.g.,RRCRestablishment); and/or RRC connection setup message (e.g.,RRCSetup). Among the one or more BWPs, at least one BWP may beconfigured as the first active BWP (e.g., BWP 1 in FIG. 23 ), one BWP asthe default BWP (e.g., BWP 0 in FIG. 23 ). The wireless device mayreceive a MAC CE to activate the SCell at n^(th) slot. The wirelessdevice may start a SCell deactivation timer (e.g.,sCellDeactivationTimer), and start CSI related actions for the SCell,and/or start CSI related actions for the first active BWP of the SCell.The wireless device may start monitoring a PDCCH on BWP 1 in response toactivating the SCell.

The wireless device may start restart a BWP inactivity timer (e.g.,bwp-InactivityTimer) at m^(th) slot in response to receiving a DCIindicating DL assignment on BWP 1. The wireless device may switch backto the default BWP (e.g., BWP 0) as an active BWP when the BWPinactivity timer expires, at s^(th) slot. The wireless device maydeactivate the SCell and/or stop the BWP inactivity timer when the SCelldeactivation timer expires.

Using the BWP inactivity timer may reduce a wireless device's powerconsumption, for example, if the wireless device is configured withmultiple cells with each cell having wide bandwidth (e.g., 1 GHzbandwidth, etc.). The wireless device may only transmit on or receivefrom a narrow-bandwidth BWP (e.g., 5 MHz) on the PCell or SCell if thereis no activity on an active BWP.

A MAC entity may perform operations, on an active BWP for an activatedserving cell (e.g., configured with a BWP), comprising: transmitting onan UL-SCH; transmitting on a RACH, monitoring a PDCCH, transmitting on aPUCCH, receiving DL-SCH, and/or (re-) initializing any suspendedconfigured uplink grants of configured grant Type 1 according to astored configuration, if any. On an inactive BWP for each activatedserving cell configured with a BWP, a MAC entity may, for example: nottransmit on an UL-SCH, not transmit on a RACH, not monitor a PDCCH, nottransmit on a PUCCH, not transmit an SRS, not receive a DL-SCHtransmission, clear configured downlink assignment(s) and/or configureduplink grant(s) of configured grant Type 2, and/or suspend configureduplink grant(s) of configured Type 1. A wireless device may perform theBWP switching to a BWP indicated by the PDCCH, for example, if thewireless device (e.g., a MAC entity of the wireless device) receives aPDCCH for a BWP switching of a serving cell and a RA procedureassociated with this serving cell is not ongoing.

A bandwidth part indicator field value may indicate an active DL BWP,from a configured DL BWP set, for DL receptions for example, if thebandwidth part indicator field is configured in DCI format 1_1. Abandwidth part indicator field value, may indicate an active UL BWP,from a configured UL BWP set, for UL transmissions, for example, if thebandwidth part indicator field is configured in DCI format 0_1.

A wireless device may be provided by a higher layer parameter a timervalue corresponding to a BWP inactivity timer for the PCell (e.g.,bwp-InactivityTimer). The wireless device may increment the timer, ifrunning, for example, every interval of 1 millisecond (or any otherfirst duration) for frequency range 1 (or any other first frequencyrange) or every 0.5 milliseconds (or any other second duration) forfrequency range 2 (or any other second frequency range), for example,if: the wireless device does not detect DCI format 1_1 for pairedspectrum operation, or the wireless device does not detect DCI format1_1 or DCI format 0_1 for unpaired spectrum operation, in the interval.

Wireless device procedures on an SCell may be similar to or the same asprocedures on a PCell, for example, if the wireless device is configuredfor the SCell with a higher layer parameter indicating a default DL BWPamong configured DL BWPs (e.g., Default-DL-BWP), and/or if the wirelessdevice is configured with a higher layer parameter indicating a timervalue (e.g., bwp-InactivityTimer). The wireless device procedures on theSCell may use the timer value for the SCell and the default DL BWP forthe SCell. The wireless device may use, as first active DL BWP and firstactive UL BWP on the SCell or secondary cell, an indicated DL BWP and anindicated UL BWP on the SCell, respectively, if a wireless device isconfigured, for example, by a higher layer parameter for the DL BWP(e.g., active-BWP-DL-SCell), and/or by a higher layer parameter for theUL BWP on the SCell or secondary cell (e.g., active-BWP-UL-SCell).

A wireless device may transmit uplink control information (UCI) via oneor more PUCCH resources to a base station. The wireless device maytransmit the one or more UCI, for example, as part of a DRX operation.The one or more UCI may comprise at least one of: HARQ-ACK information;scheduling request (SR); and/or CSI report. A PUCCH resource may beidentified by at least: frequency location (e.g., starting PRB); and/ora PUCCH format associated with initial cyclic shift of a base sequenceand time domain location (e.g., starting symbol index). A PUCCH formatmay be PUCCH format 0, PUCCH format 1, PUCCH format 2, PUCCH format 3,or PUCCH format 4. A PUCCH format 0 may have a length of 1 or 2 OFDMsymbols and be less than or equal to 2 bits. A PUCCH format 1 may occupya number between 4 and 14 of OFDM symbols and be less than or equal to 2bits. A PUCCH format 2 may occupy 1 or 2 OFDM symbols and be greaterthan 2 bits. A PUCCH format 3 may occupy a number between 4 and 14 ofOFDM symbols and be greater than 2 bits. A PUCCH format 4 may occupy anumber between 4 and 14 of OFDM symbols and be greater than 2 bits. ThePUCCH formats 1, 2, 3, and/or 4 may comprise any other quantity of OFDMsymbols and/or any other quantity of bits. The PUCCH resource may beconfigured on a PCell, or a PUCCH secondary cell.

A base station may transmit to a wireless device (e.g., if the wirelessdevice is configured with multiple uplink BWPs), one or more RRCmessages comprising configuration parameters of one or more PUCCHresource sets (e.g., at most 4 sets) on an uplink BWP of the multipleuplink BWPs. Each PUCCH resource set may be configured with a PUCCHresource set index, a list of PUCCH resources with each PUCCH resourcebeing identified by a PUCCH resource identifier (e.g.,pucch-Resourceid), and/or a maximum number of UCI information bits awireless device may transmit using one of the plurality of PUCCHresources in the PUCCH resource set.

A wireless device may select (e.g., if the wireless device is configuredwith multiple uplink BWPs) one of the one or more PUCCH resource setsbased on a total bit length of UCI information bits (e.g., HARQ-ARQbits, SR, and/or CSI) the wireless device will transmit. The wirelessdevice may select a first PUCCH resource set (e.g., with the PUCCHresource set index equal to 0, or any other PUCCH resource set index),for example, if the total bit length of UCI information bits is lessthan or equal to 2 bits (or any other quantity of bits). The wirelessdevice may select a second PUCCH resource set (e.g., with a PUCCHresource set index equal to 1), for example, if the total bit length ofUCI information bits is greater than 2 (or any other quantity of bits)and less than or equal to a first configured value. The wireless devicemay select a third PUCCH resource set (e.g., with a PUCCH resource setindex equal to 2), for example, if the total bit length of UCIinformation bits is greater than the first configured value and lessthan or equal to a second configured value. The wireless device mayselect a fourth PUCCH resource set (e.g., with a PUCCH resource setindex equal to 3), for example, if the total bit length of UCIinformation bits is greater than the second configured value and lessthan or equal to a third value.

A wireless device may determine, based on a quantity of uplink symbolsof UCI transmission and a quantity of UCI bits, a PUCCH format from aplurality of PUCCH formats comprising PUCCH format 0, PUCCH format 1,PUCCH format 2, PUCCH format 3 and/or PUCCH format 4. The wirelessdevice may transmit UCI in a PUCCH using PUCCH format 0, for example, ifthe transmission is during, greater than, or over 1 symbol or 2 symbolsand/or the quantity of HARQ-ACK information bits with positive ornegative SR (HARQ-ACK/SR bits) is 1 or 2. The wireless device maytransmit UCI in a PUCCH using PUCCH format 1, for example, if thetransmission is during, greater than, or over 4 or more symbols and thenumber of HARQ-ACK/SR bits is 1 or 2. The wireless device may transmitUCI in a PUCCH using PUCCH format 2, for example, if the transmission isduring, greater than, or over 1 symbol or 2 symbols and the number ofUCI bits is more than 2. The wireless device may transmit UCI in a PUCCHusing PUCCH format 3, for example, if the transmission is during,greater than, or over 4 or more symbols, the quantity of UCI bits ismore than 2 and a PUCCH resource does not include an orthogonal covercode. The wireless device may transmit UCI in a PUCCH using PUCCH format4, for example, if the transmission is during, greater than, or over 4or more symbols, the quantity of UCI bits is more than 2 and the PUCCHresource includes an orthogonal cover code.

A wireless device may determine a PUCCH resource from a PUCCH resourceset, for example, to transmit HARQ-ACK information on the PUCCHresource. The PUCCH resource set may be determined as described herein.The wireless device may determine the PUCCH resource based on a PUCCHresource indicator field in a DCI (e.g., with a DCI format 1_0 or DCIfor 1_1) received on a PDCCH. A PUCCH resource indicator field in theDCI may indicate one of eight PUCCH resources in the PUCCH resource set.The wireless device may transmit the HARQ-ACK information in a PUCCHresource indicated by the PUCCH resource indicator field in the DCI. ThePUCCH resource indicator field may be 3-bits (e.g., or any otherquantity of bits) in length.

The wireless device may transmit one or more UCI bits via a PUCCHresource of an active uplink BWP of a PCell or a PUCCH secondary cell.The PUCCH resource indicated in the DCI may be a PUCCH resource on theactive uplink BWP of the cell, for example, if at most one active UL BWPin a cell is supported for a wireless device.

DRX operation may be used by a wireless device, for example, to reducepower consumption, resource consumption (e.g., frequency and/or timeresources), and/or improve battery lifetime of the wireless device. Awireless device may discontinuously monitor downlink control channel(e.g., PDCCH or EPDCCH), for example, if the wireless device isoperating using DRX. The base station may configure DRX operation with aset of DRX parameters. The base station may configure the DRX operationusing an RRC configuration. The set of DRX parameters may be selected(e.g., by the base station) based on a network use case. A wirelessdevice may receive data packets over an extended delay, based on theconfigured DRX operation. The configured DRX may be used such that abase station may wait, at least until the wireless device transitions toa DRX ON state, to receive data packets. The wireless device may be in aDRX Sleep/OFF state, for example, if not receiving any data packets.

A wireless device that is configured with a DRX operation may power downat least some (or most) of its circuitry, for example, if there are nopackets to be received. The wireless device may monitor PDCCHdiscontinuously, for example, if DRX operation is configured. Thewireless device may monitor the PDCCH continuously, for example, if aDRX operation is not configured. The wireless device may listen toand/or monitor DL channels (e.g., PDCCHs) in a DRX active state, forexample, if DRX is configured. The wireless device may not listen toand/or monitor the DL channels (e.g., the PDCCHs) in a DRX Sleep state,for example, if DRX is configured.

FIG. 24 shows an example of a DRX operation. A base station (e.g., agNB) may transmit an RRC message 2502 comprising, for example, one ormore DRX parameters of a DRX cycle 2504. The RRC message may comprise:RRC connection reconfiguration message (e.g., RRCReconfiguration); RRCconnection reestablishment message (e.g., RRCRestablishment); and/or RRCconnection setup message (e.g., RRCSetup). The one or more parametersmay comprise, for example, a first parameter and/or a second parameter.The first parameter may indicate a first time value of a DRX activestate (e.g., DRX active/on duration 2508) of the DRX cycle 2504. Thesecond parameter may indicate a second time of a DRX sleep state (e.g.,DRX sleep/off duration 2512) of the DRX cycle 2504. The one or moreparameters may further comprise, for example, a time duration of the DRXcycle 2504.

The wireless device may monitor PDCCHs, for detecting one or more DCIson a serving cell, for example, if the wireless device is in the DRXactive state. The wireless device may stop monitoring PDCCHs on theserving cell, for example, if the wireless device is in the DRX sleepstate. The wireless device may monitor all PDCCHs on (or for) multiplecells that are in an active state, for example, if the wireless deviceis in the DRX active state. The wireless device may stop monitoring allPDCCH on (or for) the multiple cells, for example, if the wirelessdevice is in the DRX sleep state. The wireless device may repeat the DRXoperations according to the one or more DRX parameters.

DRX operation may be beneficial to a base station. A wireless device maytransmit periodic CSI and/or SRS frequently (e.g., based on aconfiguration), for example, if DRX is not configured. The wirelessdevice may not transmit periodic CSI and/or SRS in a DRX off period, forexample, if DRX is not configured. The base station may assign resourcesin DRX off period, that would otherwise be used for transmittingperiodic CSI and/or SRS, to the other wireless devices, for example, toimprove resource utilization efficiency.

A wireless device (e.g., a MAC entity of the wireless device) may beconfigured (e.g., by RRC) with a DRX functionality that controlsdownlink control channel (e.g., PDCCH) monitoring activity, of thewireless device, for a plurality of RNTIs for the wireless device. Theplurality of RNTIs may comprise, for example, at least one of: C-RNTI,CS-RNTI, INT-RNTI, SP-CSI-RNTI, SFI-RNTI, TPC-PUCCH-RNTI,TPC-PUSCH-RNTI, Semi-Persistent Scheduling C-RNTI, eIMTA-RNTI, SL-RNTI,SL-V-RNTI, CC-RNTI, and/or SRS-TPC-RNTI. The wireless device (e.g.,based on the wireless device being RRC_CONNECTED) may monitor the PDCCHdiscontinuously using a DRX operation, for example, if DRX isconfigured. The wireless device (e.g., the MAC entity of the wirelessdevice) may monitor the PDCCH continuously, for example, if DRX is notconfigured.

RRC may control DRX operation, for example, by configuring a pluralityof timers. The plurality of timers may comprise, for example: a DRX ONduration timer (e.g., drx-onDurationTimer), a DRX inactivity timer(e.g., drx-InactivityTimer), a downlink DRX HARQ RTT timer (e.g.,drx-HARQ-RTT-TimerDL), an uplink DRX HARQ RTT Timer (e.g.,drx-HARQ-RTT-TimerUL), a downlink retransmission timer (e.g.,drx-RetransmissionTimerDL), an uplink retransmission timer (e.g.,drx-RetransmissionTimerUL), one or more parameters of a short DRXconfiguration (e.g., drx-ShortCycle and/or drx-ShortCycleTimer)), and/orone or more parameters of a long DRX configuration (e.g.,drx-LongCycle). Time granularity for DRX timers may be defined in termsof PDCCH subframes (e.g., indicated as psf in DRX configurations), or interms of milliseconds or any other duration.

An active time of a DRX cycle may include a time duration/period inwhich at least one timer is running. The at least one timer maycomprise: a DRX ON duration timer (e.g., drx-onDurationTimer), a DRXinactivity timer (e.g., drx-InactivityTimer), a downlink retransmissiontimer (e.g., drx-RetransmissionTimerDL), an uplink retransmission timer(e.g., drx-RetransmissionTimerUL), and/or a MAC contention resolutiontimer (e.g., mac-ContentionResolutionTimer).

A DRX inactivity timer may specify a time duration/period for which thewireless device may be active based on successfully decoding a PDCCHindicating a new transmission (UL or DL or SL). The DRX inactivity timermay be restarted upon receiving PDCCH for a new transmission (UL or DLor SL). The wireless device may transition to a DRX mode (e.g., using ashort DRX cycle or a long DRX cycle), for example, based on the expiryof the DRX inactivity timer.

A DRX short cycle (e.g., drx-ShortCycle) may be a first type of DRXcycle (e.g., if configured) that may be used, for example, if a wirelessdevice enters DRX mode. An information element (e.g., DRX-Config IE) mayindicate a length of the short cycle. A DRX short cycle timer (e.g.,drx-ShortCycleTimer) may be expressed as multiples of the DRX shortcycle. The timer may indicate a number of initial DRX cycles to followthe short DRX cycle before a long DRX cycle is initiated.

A DRX ON duration timer may specify, for example, a time duration at thebeginning of a DRX cycle (e.g., DRX ON state). The drx-onDurationTimermay indicate, for example, a time duration before entering a sleep mode(e.g., DRX OFF state).

A DL HARQ RTT timer (e.g., drx-HARQ-RTT-TimerDL) may specify a minimumduration between a time at which a new transmission (e.g., a packet) isreceived and a time at which the wireless device may expect aretransmission (e.g., of the packet). The DL HARQ RTT timer may be, forexample, fixed and not configurable by RRC. The DRX HARQ RTT timer maybe, for example, configurable by RRC. A DRX HARQ RTT timer may indicatea maximum duration for which a wireless device may monitor PDCCH, forexample, if a retransmission from a base station is expected by thewireless device.

An active time of a configured DRX cycle may comprise, for example, atime at which a scheduling request (e.g., sent on PUCCH) is pending. Anactive time of a configured DXR cycle may comprise, for example, a timein which an uplink grant for a pending HARQ retransmission may occur,and in which data is present in a corresponding HARQ buffer for asynchronous HARQ process. An active time of a configured DRX cycle maycomprise, for example, a time in which a PDCCH indicating a newtransmission, addressed to the C-RNTI of the wireless device (e.g., aMAC entity of the wireless device), has not been received at thewireless device (e.g., after a successful reception of an RA response atthe wireless device). The RA response may correspond to, for example, aresponse to a preamble that is not selected by the wireless device,(e.g., the MAC entity of the wireless device).

A DL HARQ RTT timer may expire in a subframe and data of a correspondingHARQ process may not be successfully decoded, for example, at a wirelessdevice configured for DRX. A wireless device (e.g., a MAC entity of thewireless device) may start the drx-RetransmissionTimerDL for thecorresponding HARQ process. An UL HARQ RTT timer may expire in asubframe, for example, at a wireless device configured for DRX. Awireless device (e.g., a MAC entity of the wireless device) may startthe uplink retransmission timer (e.g., drx-RetransmissionTimerUL) for acorresponding HARQ process. A DRX command MAC CE or a long DRX commandMAC CE may be received, for example, at a wireless device configured forDRX. A wireless device (e.g., a MAC entity of the wireless device) maystop the DRX ON duration timer (e.g., drx-onDurationTimer) and stop theDRX inactivity timer (e.g., drx-InactivityTimer).

A DRX inactivity timer (e.g., drx-InactivityTimer) may expire or a DRXcommand MAC CE may be received in a subframe, for example, at a wirelessdevice configured for DRX. A wireless device (e.g., a MAC entity of thewireless device) may start or restart DRX short cycle timer (e.g.,drx-ShortCycleTimer) and may use a short DRX Cycle, for example, if theshort DRX cycle is configured. The wireless device (e.g., the MAC entityof the wireless device) may use a long DRX cycle, if the long DRX cycleis configured.

A DRX short cycle timer (e.g., drx-ShortCycleTimer) may expire in asubframe, for example, at a wireless device configured for DRX. Awireless device (e.g., a MAC entity of the wireless device) may use thelong DRX cycle (e.g., based on expiration of the drx-ShortCycleTimer). Along DRX command MAC CE may be received. The wireless device (e.g., theMAC entity of the wireless device) may stop a DRX short cycle timer(e.g., drx-ShortCycleTimer) and may use the long DRX cycle (e.g., basedon reception of the long DRX command MAC CE).

A wireless device that is configured for DRX operation may start a DRXON duration timer (e.g., drx-onDurationTimer), for example, if a shortDRX cycle is used and if equation (1) is valid.[(SFN×10)+sub frame number]modulo (drx−ShortCycle)=(drxStartOffset)modulo (drx−ShortCycle)  Equation (1)is valid. A wireless device that is configured for DRX operation maystart a DRX ON duration timer (e.g., drx-onDurationTimer), for example,if a long DRX Cycle is used and if equation (2) is valid[(SFN*10)+sub frame number]modulo(drx−longCycle)=drxStartOffset  Equation (2)

FIG. 25 shows example of DRX operation. A base station may send (e.g.,transmit) an RRC message to a wireless device. The RRC message maycomprise configuration parameters of DRX operation. The base station maysend (e.g., transmit), via a PDCCH, DCI for downlink resourceallocation, to the wireless device. The wireless device may start a DRXinactivity timer (e.g., drx-InactivityTimer) and may monitor the PDCCH.The wireless device may receive a transmission block (TB), for example,while the DRX inactivity timer is running. The wireless device may starta HARQ RTT timer (e.g., drx-HARQ-RTT-TimerDL), and may stop monitoringthe PDCCH, for example, based on receiving the TB. The wireless devicemay transmit a NACK to the base station, for example, if the wirelessdevice fails to receive the TB. The wireless device may monitor thePDCCH and start a HARQ retransmission timer (e.g.,drx-RetransmissionTimerDL), for example, based on an expiration of theHARQ RTT Timer. The wireless device may receive second DCI, for example,while the HARQ retransmission timer is running. The second DCI mayindicate, for example, a DL grant for a retransmission of the TB. Thewireless device may stop monitoring the PDCCH, for example, if thewireless device fails to receive a second DCI before an expiration ofthe HARQ retransmission timer.

The base station may transmit first DCI for an uplink grant via a PDCCH,to the wireless device. The wireless device may start the DRX inactivitytimer and monitor the PDCCH. The wireless device may start a HARQ RTTTimer (e.g., drx-HARQ-RTT-TimerUL) and stop monitoring the PDCCH, forexample, based on (e.g., after or in response to) transmitting a TB viathe uplink grant. The base station may transmit a NACK to the wirelessdevice, for example, if the base station is unsuccessful in receivingthe TB. The wireless device may start a HARQ retransmission timer (e.g.,drx-RetransmissionTimerUL) and monitor the PDCCH for the NACK, forexample, if/when the HARQ RTT Timer expires. The wireless device mayreceive second DCI indicating an uplink grant for the retransmission ofthe TB, for example, if/when the HARQ retransmission timer is running.The wireless device may stop monitoring the PDCCH, for example, if/whenthe wireless device does not receive the second DCI before the HARQretransmission timer expires.

A wireless device may receive an uplink grant dynamically on a PDCCH orin a random-access response (RAR). The wireless device may receive anuplink grant configured semi-persistently by an RRC message. Thewireless device may transmit, via the uplink grant, an uplink TB on aUL-SCH. A layer (e.g., medium access control (MAC) layer) of thewireless device may receive HARQ information from lower layers (e.g.,physical layer) of the wireless device, for example, for transmission ofthe uplink TB. The HARQ information may comprise at least one of: HARQprocess indicator/identifier (ID); new data indicator (NDI); redundancyversion (RV); and/or transport block size (TBS).

A wireless device (e.g., a MAC entity of the wireless device) may beassociated with a C-RNTI, a Temporary C-RNTI (TC-RNTI), or a configuredscheduling RNTI (CS-RNTI). A wireless device may receive an uplink grantfor a serving cell on a PDCCH for the MAC entity's C-RNTI or TC-RNTI.The MAC entity may deliver the uplink grant and one or more associatedHARQ information to the HARQ entity, for example, for each PDCCHoccasion and for each serving cell belonging to a time alignment group(TAG) that has a running timer (e.g., timeAlignmentTimer) and for eachuplink grant received for a PDCCH occasion.

A wireless device (e.g., a MAC entity of the wireless device) maycomprise a HARQ entity for each serving cell with configured uplink. Thewireless device may be configured with a supplementary uplink. The HARQentity may maintain a quantity of parallel HARQ processes. Each HARQprocess of the quantity of parallel HARQ processes may support one TB,and the HARQ process may be associated with a HARQ processindicator/identifier (ID). A HARQ process indicator/identifier (e.g.,identifier 0) may correspond to uplink transmission with uplink grant inan RAR process.

A PUSCH aggregation factor parameter (e.g., pusch-AggregationFactor) mayprovide a quantity of transmissions of a TB within a bundle of a dynamicgrant. A wireless device (e.g., a MAC entity of the wireless device) maybe configured with PUSCH repetition (e.g., pusch-AggregationFactor>1).(pusch-AggregationFactor−1) HARQ retransmissions may follow within abundle, for example, based on/after an initial transmission. A parameter(e.g., repK) may provide a quantity of transmissions of a TB within abundle of a configured uplink grant. A wireless device (e.g., a MACentity of the wireless device) may be configured with a value of repKthat is greater than 1. HARQ retransmissions may follow within a bundle,for example, based on/after the initial transmission. Bundling operationmay rely on the HARQ entity for both dynamic grant and configured uplinkgrant. The bundling operation may rely on the HARQ entity for invokingthe same HARQ process for each transmission that is part of the samebundle. HARQ retransmissions may be triggered within a bundle, forexample, with or without waiting for feedback from previous transmissionaccording to the PUSCH aggregation factor (e.g., for the dynamic grant)and/or the repK parameter (e.g., for the configured uplink grant). Eachtransmission within a bundle may be a separate uplink grant, forexample, after the initial uplink grant within a bundle is delivered tothe HARQ entity.

A sequence of redundancy versions, for each transmission within a bundleof a dynamic grant, may be determined based on one or more fields of aDCI carrying the dynamic grant. A sequence of redundancy versions, foreach transmission within a bundle of a configured uplink grant, may bedetermined based on one or more configuration parameters in an RRCmessage.

A HARQ entity of a wireless device may indicate (e.g., identify) a HARQprocess associated with an uplink grant. The HARQ entity may obtain,from a multiplexing and assembly entity, a MAC PDU to transmit, forexample, if the received uplink grant is not addressed to a TC-RNTI onPDCCH, and an NDI provided in the associated HARQ information has beentoggled compared to an NDI value in the previous transmission of the TBof the HARQ process. The HARQ entity may deliver the MAC PDU, the uplinkgrant, and the HARQ information of the TB to the indicated/identifiedHARQ process and instruct the identified HARQ process to trigger a newtransmission, for example, based on obtaining the MAC PDU. The HARQentity may deliver the uplink grant and the HARQ information (e.g.,redundancy version) of the TB to the indicated/identified HARQ process,and instruct the indicated/identified HARQ process to trigger aretransmission, for example, if the received uplink grant is addressedto a TC-RNTI on PDCCH, or the NDI provided in the associated HARQinformation has not been toggled compared to the NDI value in theprevious transmission of the TB of the HARQ process.

A HARQ process may be associated with a HARQ buffer. A wireless devicemay perform a new transmission on a resource and with an MCS indicatedon either a PDCCH, an RAR, or an RRC message. The wireless device mayperform a retransmission on a resource and with an MCS (if provided) asindicated on PDCCH. The wireless device may perform a retransmission ona same resource and with a same MCS as was used for a last transmissionattempt within a bundle.

The HARQ process may store the MAC PDU in the associated HARQ buffer,store the uplink grant received from the HARQ entity, and/or generate atransmission for a TB, for example, if the HARQ entity requests a newtransmission of the TB. The HARQ process may store the uplink grantreceived from the HARQ entity and generate a transmission for a TB, forexample, if the HARQ entity requests a retransmission for the TB. TheHARQ process may instruct the physical layer to generate a transmissionfor a TB according to the stored uplink grant, for example, if the MACPDU was obtained from a Msg3 buffer or if there is no measurement gap atthe time of the transmission. The HARQ process may instruct the physicallayer to generate a retransmission for a TB according to the storeduplink grant, for example, if the retransmission does not collide with atransmission for the MAC PDU obtained from the Msg3 buffer.

FIG. 26 shows an example of an uplink TB retransmission mechanism basedon a HARQ procedure. A base station 2602 may send (e.g., transmit), to awireless device 2604, first DCI comprising an uplink grant and HARQinformation. The HARQ information may comprise a HARQ processindicator/identifier (ID) (e.g., process ID=k) and a first NDI value(e.g., 1).

The wireless device 2604 may store an NDI value (e.g., in a memoryassociated with the wireless device). The memory may be associated witha HARQ process identified by a HARQ process ID. The NDI value may beassociated with a HARQ process identified by a HARQ process ID. Thewireless device 2604 may have (e.g., store) an initial NDI value (e.g.,0), for example, before receiving the first DCI. The wireless device2604 may receive the first DCI. The wireless device 2604 may determinethat the first NDI value (e.g., 1) is different from the initial NDIvalue (e.g., 0). The wireless device 2604 may determine that the firstNDI value is toggled with respect to the initial NDI value. The wirelessdevice 2604 (e.g., a HARQ entity of the wireless device 2604) maydetermine/obtain a MAC PDU (e.g., from a multiplexing and assemblyentity of the wireless device 2604), for example, based on the first NDIvalue being different from the initial NDI value. The HARQ entity maydeliver the MAC PDU, the uplink grant, and the HARQ information to aHARQ process indicated/identified by the HARQ process ID (e.g., processID=k). The HARQ entity may instruct the HARQ process to trigger a newtransmission for a TB that comprises the MAC PDU. The HARQ process maystore the MAC PDU in an associated HARQ buffer and store the uplinkgrant. The HARQ process may instruct the wireless device 2604 (e.g., aphysical layer of the wireless device 2604) to generate a newtransmission for the TB, for example, based on the stored uplink grant.At or after time t₁, the wireless device 2604 may send (e.g., transmit)the TB based on the stored uplink grant. The wireless device 2604 mayset the first NDI value (e.g., 1) as a new NDI value, for example, basedon the transmission of the TB.

The base station 2602 may provide a subsequent uplink grant, to thewireless device 2604, for a retransmission of the TB. The base station2602 may provide the subsequent uplink grant, for example, if the basestation 2602 does not successfully receive the TB transmitted by thewireless device 2604. The base station 2602 may transmit a second DCIindicating the retransmission of the TB. The second DCI may comprise asame HARQ process ID as the first HARQ process ID, a second uplinkgrant, a RV value, and a second NDI value (e.g., 1). The wireless device2604 may determine the second NDI value is equal to/same as the firstNDI value/the new NDI value. The wireless device 2604 may determine thatthe second NDI value is not toggled with respect to the new NDIvalue/the first NDI value. The HARQ entity may deliver, to the HARQprocess, the second uplink grant and the RV value. The HARQ entity mayinstruct the HARQ process to trigger a retransmission of the TB, forexample, based on the second NDI value being equal to the new NDI value.The HARQ process may store the second uplink grant. The HARQ process mayinstruct the wireless device 2604 (e.g., the physical layer of thewireless device 2604) to generate a retransmission for the TB accordingto the second uplink grant. At or after time t₂, the wireless device2604 may resend (e.g., retransmit) the TB based on the second uplinkgrant.

FIG. 27 shows an example of an uplink TB transmission mechanism based onHARQ procedure. A base station 2702 may transmit to a wireless device2704, first DCI (e.g., comprising an uplink grant) and HARQ information.The HARQ information may comprise a HARQ process indicator/ID (e.g.,process ID=k) and a first NDI value (e.g., 1).

The wireless device 2704 may store an NDI value (e.g., in a memory,associated with a HARQ process identified by a HARQ process ID, of thewireless device). The NDI value may be associated with a HARQ processidentified by the HARQ process ID. The wireless device 2704 may have aninitial NDI value (e.g., 0), for example, prior to receiving the firstDCI. The wireless device 2704 may receive the first DCI The wirelessdevice 2704 may determine that the first NDI has (e.g., 1) is differentfrom the initial NDI value (e.g., 0). The wireless device 2704 maydetermine that the first NDI value is toggled with respect to theinitial NDI value. The wireless device 2704 (e.g., a HARQ entity of thewireless device 2704) may obtain a MAC PDU (e.g., from a multiplexingand assembly entity of the wireless device), for example, based on thefirst NDI value being different from the initial NDI value. The HARQentity may deliver the MAC PDU, the uplink grant and the HARQinformation to a HARQ process identified by the HARQ process ID (e.g.,process ID=k). The HARQ entity may instruct the HARQ process to triggera new transmission for a first TB comprising the MAC PDU. The HARQprocess may store the MAC PDU in an associated HARQ buffer and store theuplink grant. The HARQ process may instruct the wireless device 2704(e.g., a physical layer of the wireless device 2704) to generate a newtransmission for the first TB, for example, based on the stored uplinkgrant. At or after time t₁, the wireless device 2704 (e.g., the physicallayer of the wireless device 2704) may transmit the first TB based onthe stored uplink grant. The wireless device may set the first NDI value(e.g., 1) as a new NDI value, for example, based on transmission of thefirst TB.

The base station 2702 may provide a subsequent uplink grant, to thewireless device 2704, for transmitting a second TB. The base station2702 may provide the subsequent uplink grant, for example, after thebase station 2702 successfully receives the first TB. The base station2702 may transmit a second DCI indicating the new transmission. Thesecond DCI may comprise a same HARQ process ID as the first HARQ processID, a second uplink grant, a RV value, and a second NDI value (e.g., 0).The wireless device 2704 may determine that the second NDI value isdifferent from the first NDI value (e.g., 1)/the new NDI value. Thewireless device 2704 may determine that the second NDI value is toggledwith respect to the new NDI value. A HARQ entity of the wireless device2704 may determine/obtain a second MAC PDU (e.g., from the multiplexingand assembly entity), for example, based on the second NDI value beingdifferent from (e.g., toggled with respect to) first NDI value/new NDIvalue. The HARQ entity may deliver the second MAC PDU, the second uplinkgrant, and second HARQ information to the HARQ process (e.g., identifiedby process ID=k). The HARQ entity may instruct the HARQ process totrigger a new transmission for the second TB (e.g., comprising thesecond MAC PDU). The HARQ process may store the second MAC PDU in anassociated HARQ buffer and store the second uplink grant. The HARQprocess may instruct the wireless device 2704 (e.g., the physical layerof the wireless device 2704) to generate a new transmission for thesecond TB according to the second uplink grant. At or after time t₂, thewireless device 2704 may transmit the second TB according to the seconduplink grant.

A communication protocol (e.g., 4G or 5G wireless communicationprotocol) may support multiple types of services. Wireless devices(e.g., operating according to the communication protocol) may transmitdifferent data packets for the different services. The multiple types ofservices may comprise, for example, at least one of: an ultra-reliablelow-latency communication (URLLC); an enhanced mobile broadband service(eMBB); a machine type communication (MTC); and/or a vehicle to vehicle(or vehicle to everything) communication (V2X). A first data packet(e.g., a URLLC data packet) of a first wireless device may bemultiplexed with a second data packet (e.g., an eMBB data packet) of asecond wireless device (e.g., on a PUSCH resource). The first datapacket may be transmitted with a first transmission format (e.g., afirst numerology or a first scheduling granularity) on a first PUSCHresource. The second data packet may be transmitted with a secondtransmission format (e.g., a second numerology or a second schedulinggranularity) on a second PUSCH resource. The first PUSCH resource may bea portion of the second PUSCH resource. The first PUSCH resource mayoverlap (e.g., fully or partially) in time with the second PUSCHresource. The second PUSCH resource may be allocated for the secondwireless device by an uplink grant indicated via a PDCCH. The first datapacket of the first wireless device may be transmitted on the firstPUSCH resource, for example, if the first data packet is associated witha lower latency than the second data packet. The first data packet andsecond data packets may be associated with respective (e.g., same ordifferent) service types. The base station may receive the first datapacket from the first wireless device on the first PUSCH resource andthe second data packet from the second wireless device on the secondPUSCH resource. Reception of the first data packet on the first PUSCHresource may result in reception/decoding errors at the base station,for example, if the first PUSCH resource is a portion of the secondPUSCH resource (e.g., used for transmission of the second data packetfrom the second wireless device). The base station may wrongly detectthat the second data packet from the second wireless device is a part offirst data packet from the first wireless device.

A wireless device (e.g., operating according to the communicationprotocol) may transmit different data packets for different services(e.g., a URLLC service, an eMBB service, an MTC service, a V2X service,etc.). A first data packet (e.g., a URLLC data packet) of the wirelessdevice may be multiplexed with a second data packet (e.g., an eMBB datapacket) of the wireless device (e.g., on a PUSCH resource). The firstdata packet may be transmitted with a first transmission format (e.g., afirst numerology or a first scheduling granularity) on a first PUSCHresource. The second data packet may be transmitted with a secondtransmission format (e.g., a second numerology or a second schedulinggranularity) on a second PUSCH resource. The first PUSCH resource may bea portion of the second PUSCH resource. The first PUSCH resource mayoverlap (e.g., fully or partially) in time with the second PUSCHresource. The second PUSCH resource may be allocated for the secondwireless device by an uplink grant indicated via a PDCCH. The first datapacket of the first wireless device may be transmitted on the firstPUSCH resource, for example, if the first data packet is associated witha lower latency than the second data packet. The first data packet andsecond data packets may be associated with respective (e.g., same ordifferent) service types. The base station may receive the first datapacket on the first PUSCH resource and the second data packet on thesecond PUSCH resource. Reception of the first data packet on the firstPUSCH resource may result in reception/decoding errors at the basestation, for example, if the first PUSCH resource is a portion of thesecond PUSCH resource (e.g., used for transmission of the second datapacket from the wireless device). The base station may wrongly detectthat the second data packet is a part of first data packet.

A base station may cancel or delay (e.g., pre-empt) transmission oflower priority data (e.g., eMBB data) from a first wireless device, forexample, if the lower priority data may overlap (e.g., in time and/orfrequency) with higher priority data (e.g., URLLC data) from a secondwireless device. A base station may pre-empt transmission of first datacorresponding to a first transmission format (e.g., from a firstwireless device), for example, if the first data overlaps (e.g., in timeand/or frequency) with data corresponding to a second transmissionformat.

A base station may cancel or delay (e.g., pre-empt) transmission oflower priority data (e.g., eMBB data) from a wireless device, forexample, if the lower priority data may overlap (e.g., in time and/orfrequency) with higher priority data (e.g., URLLC data) from thewireless device. A base station may pre-empt transmission of first datacorresponding to a first transmission format, for example, if the firstdata overlaps (e.g., in time and/or frequency) with data correspondingto a second transmission format.

A base station may transmit DCI comprising fields indicating one or moreuplink pre-emption indications to a wireless device (e.g., the secondwireless device) or a group of wireless devices (e.g., comprising thesecond wireless device), indicating if one or more time/frequencyresources are pre-empted (e.g., reserved for the first wireless device).

FIG. 28 shows an example uplink pre-emption mechanism. A base station2802 may transmit to a wireless device 2804, first DCI comprising afirst uplink grant. The uplink grant may comprise/indicate PUSCHresources for uplink transmissions. The wireless device 2804 may startsending (e.g., transmitting) a TB on the first uplink grant, forexample, based on receiving the DCI. The wireless device 2804 mayreceive an uplink pre-emption indication from the base station. Theuplink pre-emption indication may comprise a cancellation indication, astop indication, and/or a suspend indication. The uplink pre-emptionindication may indicate that at least a part of the PUSCH resources ispre-empted, and/or the wireless device 2804 may stop uplink transmissionon the at least part of the PUSCH resources. The wireless device 2804may stop the ongoing uplink transmission on the at least part of thePUSCH resources, wherein the at least part of the PUSCH resources arepre-empted based on the uplink pre-emption indication, for example,based on the uplink pre-emption indication. The base station 2802 maytransmit DCI comprising the uplink pre-emption indication. The DCI maybe transmitted to a wireless device addressed by a C-RNTI, or betransmitted to a group of wireless devices addressed by a group RNTI.The base station 2802 may transmit a MAC CE comprising the uplinkpre-emption indication. The base station 2802 may transmit a signalsequence (e.g., a CSI-RS/DMRS) comprising the uplink pre-emptionindication. The base station 2802 may transmit second DCI to a secondwireless device (e.g., a URLLC wireless device). The second DCI mayindicate a second uplink grant comprising the at least part of the PUSCHresources, where the PUSCH resources are allocated in the first DCI forthe wireless device 2804. The second wireless device may transmit uplinkdata via the second uplink grant, for example based on (e.g., inresponse to) receiving the second DCI.

The base station 2802 may transmit second DCI to the wireless device2804, where the second DCI indicates a transmission of a second uplinkdata (e.g., an uplink data unit associated with low transmissionlatency, e.g., an uplink data associated with a URLLC service). Thesecond DCI may indicate a second uplink grant comprising the at leastpart of the PUSCH resources, where the PUSCH resources are allocated inthe first DCI for the first wireless device 2804. The wireless device2804 may transmit the second uplink data via the second uplink grant,for example based on (e.g., in response to) receiving the second DCI.

FIG. 29 shows an example uplink pre-emption mechanism. A scheduled(e.g., upcoming) uplink transmission may be canceled based on an uplinkpre-emption indication. A base station 2902 may transmit to a wirelessdevice 2904, first DCI comprising a first uplink grant. The uplink grantmay comprise PUSCH resources. The wireless device 2904 may generate a TBbased on the first DCI. The wireless device 2904 may receive an uplinkpre-emption indication from the base station, for example, prior tostarting an uplink transmission of the TB. The uplink pre-emptionindication may comprise a cancellation indication, a stop indication,and/or a suspension indication. The uplink pre-emption indication mayindicate that at least a part of the PUSCH resources is pre-empted,and/or the wireless device 2904 may stop uplink transmission on the atleast part of the PUSCH resources. The wireless device 2904 may stopscheduled (e.g., upcoming) uplink transmission on the at least part ofthe PUSCH resources, wherein the at least part of the PUSCH resourcesare pre-empted based on the uplink pre-emption indication. The basestation 2902 may transmit DCI comprising the uplink pre-emptionindication. The DCI may be transmitted to a wireless device addressed bya C-RNTI, or be transmitted to a group of wireless devices addressed bya group RNTI. The base station 2902 may transmit a MAC CE comprising theuplink pre-emption indication. The base station 2902 may transmit asignal sequence (e.g., a CSI-RS/DMRS) comprising the uplink pre-emptionindication. The base station 2902 may transmit second DCI to a secondwireless device (e.g., a URLLC wireless device), for example, based on(e.g., after or in response to) transmitting the uplink pre-emptionindication. The second DCI may indicate a second uplink grant comprisingthe at least part of the PUSCH resources, where the PUSCH resources areallocated in the first DCI for the first wireless device 2904. Thesecond wireless device may transmit uplink data via the second uplinkgrant, for example, based on receiving the second DCI.

FIG. 30 shows an example of group uplink cancellation based on an uplinkpre-emption indication. A base station 3002 may send (e.g., transmit) toa wireless device 3004, first DCI comprising a first uplink grant. Thefirst uplink grant may comprise first PUSCH resources. The base station3002 may send (e.g., transmit) to a wireless device 3006, second DCIcomprising a second uplink grant. The second uplink grant may comprisesecond PUSCH resources. The base station 3002 may send (e.g., transmit)an uplink pre-emption indication to the wireless device 3004 and thewireless device 3006, for example, in a group command DCI.

At or after time t₁, the wireless device 3004 may send (e.g., transmit)an uplink transmission 3008 on the first uplink grant. The wirelessdevice 3004 may receive the uplink pre-emption indication, for example,after wireless device 3004 starts the uplink transmission 3008 on thefirst uplink grant. The wireless device 3006 may receive the uplinkpre-emption indication, for example, prior to the wireless device 3006starting an uplink transmission on the second uplink grant.

The uplink pre-emption indication may comprise a cancellationindication, a stop indication, a suspension indication, or any otherindication. The base station 3002 may transmit DCI comprising the uplinkpre-emption indication. The DCI may be transmitted to a group ofwireless devices (e.g., wireless device 3004 and wireless device 3006)addressed by a group RNTI.

At or after time t₂, the wireless device 3004 may stop the uplinktransmission 3008, for example, based on the uplink pre-emptionindication. The wireless device 3006 may be pre-empted from any uplinktransmission, for example, based on the uplink pre-emption indication.The wireless device 3006 may not start the uplink transmission 3010, forexample, based on the uplink pre-emption indication. The uplinkpre-emption indication may indicate that any uplink transmission fromthe wireless device 3006 may be stopped at a first symbol that isearlier than a second symbol on which the uplink transmission 3010 isscheduled to begin.

The wireless device 3004 may stop ongoing uplink transmission 3008 on atleast first part of the first uplink grant, for example, based on theuplink pre-emption indication. The wireless device 3006 may stopscheduled uplink transmission 3010 on at least second part of the seconduplink grant, based on the uplink pre-emption indication. The uplinkpre-emption indication may indicate that the at least first part of thefirst uplink grant is pre-empted, and/or the at least second part of thesecond uplink grant is pre-empted. The base station 3002 may transmit athird DCI to a third wireless device (e.g., a URLLC wireless device),for example, based on (e.g., after or in response to) transmitting theuplink pre-emption indication. The third DCI may indicate a third uplinkgrant comprising the at least first part of the first uplink grantand/or the at least second part of the second uplink grant. The thirdwireless device may transmit uplink data via the third uplink grant, forexample, based on (e.g., after or in response) to receiving the thirdDCI.

A wireless device may receive an uplink grant (e.g., in first DCI or anRRC message). The uplink grant may be dynamic or sem-persistent. Thewireless device may receive a message (e.g., an uplink pre-emptionindication) cancelling an uplink transmission via the uplink grant. Thewireless device may cancel the uplink transmission (e.g., ongoing orscheduled) on an uplink grant, for example, based on receiving theuplink pre-emption indication. The wireless device may receive a newuplink grant (e.g., in second DCI), for example, after canceling theuplink transmission. The wireless device may determine if an NDI valuereceived in the second DCI is different from (e.g., toggled with respectto) a a stored NDI value stored at the wireless device.

The wireless device may be unable to set a value of a stored NDI, forexample, if the wireless device cancels the uplink transmission of theTB based on the uplink pre-emption indication. The wireless device maybe unable to determine whether the new uplink grant in the second DCI isfor a new transmission or a retransmission, for example, if the wirelessdevice is unable to set a value of stored NDI. For example, it may beunclear whether the wireless device should treat the cancelled uplinktransmission as a transmission which has been performed, whether thewireless device should treat the cancelled uplink transmission as atransmission that has not been performed, or whether the wireless deviceshould treat the cancelled uplink transmission in any other manner(e.g., as cancelled or not cancelled based on one or more criteria). Abase station and a wireless device may not be aligned with respect to astatus of an NDI value stored in the wireless device, for example, ifthe wireless device cancels (or does not cancel) the uplink transmissionof the TB based on the uplink pre-emption indication and the basestation may not be informed of such cancellation (or lack ofcancellation).

A base station may request an initial transmission of a first TB, and awireless device may incorrectly retransmit a second TB, for example, ifthe wireless device is unable to set a value of a stored NDI. The basestation may request a retransmission of a first TB, and the wirelessdevice may incorrectly transmit a second TB, for example, if thewireless device is unable to set a value of a stored NDI. This lack ofbase station and wireless device synchronization may result in reducedsystem throughput, increased data transmission latency, and/or increasedpower consumption of the wireless device.

Various examples described herein may improve performance by aligning abase station and a wireless device with respect a status of an uplinktransmission process (e.g., a HARQ process). A base station and awireless device may be aligned with respect to a status of a dataindicator (e.g., an NDI value) stored in the wireless device, forexample, if an uplink transmission is cancelled. The wireless device maydetermine/assume (or consider) that the uplink transmission has beenperformed, for example, even if the uplink transmission is cancelled.The wireless device may determine/assume (or consider) that an uplinktransmission of a TB has been performed, for example, based on/inresponse to the uplink transmission being cancelled (e.g., based on apre-emption indication or any other indication). The wireless device maydetermine/assume (or consider) that an uplink transmission of a TB hasbeen performed, for example, based on/in response to the uplinktransmission being deprioritized (e.g., based on a pre-emptionindication or any other indication). The wireless device may store adata indicator (e.g., an NDI) received in control information (e.g.,DCI) comprising an uplink grant and/or store a data unit (e.g., a MACPDU) associated with a HARQ process in response to an uplinktransmission via the uplink grant, of a TB associated with the HARQprocess being cancelled (e.g., based on the pre-emption indication).Storing the data indicator received in the control information (e.g.,even if the uplink transmission is cancelled) and/or storing the dataunit (e.g., the MAC PDU) may enable the wireless device and the basestation to be aligned with respect to a status of the uplinktransmission process. Alignment of the base station and the wirelessdevice may enable the base station to request a retransmission of thedata unit or a transmission of a next data unit with lower signalingoverhead and error rates. Storing the data unit may enable fasterresponse times at the wireless device. The enhancements described hereinmay improve system throughput, reduce data transmission latency, and/orreduce power consumption of the wireless device.

FIG. 31 shows an example of enhanced HARQ procedure. The HARQ proceduremay support an uplink pre-emption indication. A base station 3102 maytransmit to a wireless device 3104, first DCI 3106. The first DCI 3106may comprise an uplink grant and first HARQ information. The first HARQinformation may comprise a HARQ process indicator/ID (e.g., processID=k) and a first NDI value (e.g., 1).

The wireless device 3104 may store an NDI value (e.g., in a memory,associated with a HARQ process identified by the HARQ process ID, of thewireless device). The NDI value may be associated with a HARQ processidentified by a HARQ process ID. The wireless device 3104 may (may havean initial NDI value (e.g., 0), for example, before receiving the firstDCI 3106. The wireless device 3104 may determine that the first NDIvalue (e.g., 1) is different from the initial NDI value (e.g., 0). Thewireless device 3104 may determine that the first NDI value is toggledwith respect to the initial NDI value. The wireless device 3104 (e.g.,the HARQ entity of the wireless device 3104) may obtain a MAC PDU (e.g.,from a multiplexing and assembly entity of the wireless device 3104),for example. based on the first NDI value being different from theinitial NDI value. The HARQ entity may deliver the MAC PDU, the uplinkgrant, and the first HARQ information to a HARQ process identified bythe HARQ process ID (e.g., process ID=k). The HARQ entity may instructthe HARQ process to trigger an initial (or a new) transmission for afirst TB comprising the MAC PDU. The HARQ process may store the MAC PDUin an associated HARQ buffer and store the uplink grant. The HARQprocess may instruct the wireless device 3104 (e.g., the physical layerof the wireless device 3104) to generate the initial (or the new)transmission for the first TB, for example, based on the stored uplinkgrant.

The wireless device 3104 (e.g., the physical layer of the wirelessdevice 3104) may receive an uplink pre-emption indication 3108 from thebase station 3102. The wireless device 3104 may receive the uplinkpre-emption indication 3108 from the base station 3102, for example,prior to starting a transmission for a first TB based on the storeduplink grant. The uplink pre-emption indication 3108 may indicate thatthe wireless device 3104 may cancel/suspend/stop the transmission forthe first TB on at least one of PUSCH resources of the uplink grant. Thewireless device 3104 (e.g., the physical layer of the wireless device3104) may cancel the transmission for the first TB on the at least oneof the PUSCH resources of the uplink grant. The wireless device 3104(e.g., a HARQ entity of the wireless device 3104) may store the firstNDI value as a new NDI value and/or store a MAC PDU associated with thefirst TB in response to cancelling the transmission for the first TB.The HARQ entity of the wireless device 3104 may consider that the firstTB has been transmitted by the wireless device 3104, for example, evenif the wireless device 3104 has cancelled the transmission of the firstTB based on the uplink pre-emption indication 3108.

The wireless device 3104 (e.g., the physical layer of the wirelessdevice 3104) may receive second DCI 3110. The second DCI 3110 maycomprise a same HARQ process ID as the first HARQ process ID, a seconduplink grant, an RV value, and a second NDI value (e.g., 1). Thephysical layer may deliver the second uplink grant and second HARQinformation (e.g., the first HARQ process ID, the RV value, and/or thesecond NDI value) to a MAC layer of the wireless device 3104. The MAClayer may deliver the uplink grant and the one or more HARQ informationto a HARQ entity of the wireless device 3104. The HARQ entity maydetermine/identify a HARQ process, for example, based on the first HARQprocess ID in the second DCI 3110. The HARQ entity may determine if thesecond NDI value is the different from (e.g., toggled with respect to)the new NDI value/the first NDI value. The HARQ entity may determinethat the second NDI value (e.g., 1) is the same as/substantially thesame as (e.g., not toggled with respect to) the new NDI value/the firstNDI value (e.g., 1).

The HARQ entity may instruct the HARQ process to trigger aretransmission of the first TB, for example, based on the second NDIvalue (e.g., 1) being the same as/substantially the same as (e.g., nottoggled with respect to) the new NDI value/the first NDI value. The HARQprocess may instruct the wireless device 3104 (e.g., the physical layerof the wireless device 3104) to generate a retransmission of the firstTB. The wireless device 3104 (e.g., the physical layer of the wirelessdevice 3204) may retransmit the first TB according to the second uplinkgrant. The wireless device 3104 (e.g., the HARQ entity of the wirelessdevice 3104) may store the first NDI value as the new NDI value, forexample, before cancelling uplink transmission based on the uplinkpre-emption indication 3108. The HARQ entity may determine (e.g.,assume/consider) that the TB has been transmitted by the physical layer,for example, even if the physical layer has cancelled the uplinktransmission based on the uplink pre-emption indication 3108. The HARQentity may correctly determine if an initial transmission or aretransmission is required, for example, based on receiving the secondDCI 3110 with the second NDI value and based on a comparison between thesecond NDI value and the stored new NDI value. This may enable alignmentbetween the base station 3102 and the wireless device 3104 with respectto a status of an uplink HARQ process that supports an uplinkpre-emption mechanism (e.g., for multiplexing different transmissionswith different transmission formats). The alignment may improve systemthroughput, reduce data transmission latency, and/or reduce powerconsumption of the wireless device 3104.

FIG. 32 shows an example of enhanced HARQ procedure. The HARQ proceduremay support uplink pre-emption indication. A base station 3202 maytransmit to a wireless device 3204, first DCI 3206. The first DCI 3206may comprise an uplink grant and first HARQ information. The first HARQinformation may comprise a HARQ process ID (e.g., process ID=k as shownin FIG. 32 ) and a first NDI value (e.g., 1).

The wireless device 3104 may store an NDI value (e.g., in a memoryassociated with the wireless device). The NDI value may be associatedwith a HARQ process identified by a HARQ process ID. The wireless device3104 may have an initialNDI value (e.g., 0), for example, beforereceiving the first DCI 3206. The wireless device 3204 may determinethat the first NDI value (e.g., 1) is different from the initial NDIvalue (e.g., 0). The wireless device 3204 may determine that the firstNDI value is toggled with respect to the initial NDI value. The wirelessdevice 3204 (e.g., a HARQ entity of the wireless device 3204) may obtaina MAC PDU (e.g., from a multiplexing and assembly entity of the wirelessdevice 3204), for example, based on the first NDI value being differentfrom the initial NDI value. The HARQ entity may deliver the MAC PDU, theuplink grant and the first HARQ information to a HARQ process identifiedby the HARQ process ID (e.g., process ID=k). The HARQ entity mayinstruct the HARQ process to trigger an initial (or a new) transmissionfor a first TB comprising the MAC PDU. The HARQ process may store theMAC PDU in an associated HARQ buffer, and store the uplink grant. TheHARQ process may instruct the wireless device 3204 (e.g., the physicallayer of the wireless device 3204) to generate an initial (or a new)transmission for the first TB according to the stored uplink grant.

The wireless device 3204 (e.g., the physical layer of the wirelessdevice 3204) may receive, from the base station 3202, an uplinkpre-emption indication 3208. before starting a transmission of a firstTB according to an uplink grant. The uplink pre-emption indication 3208may indicate that the wireless device 3204 may cancel/suspend/stop)transmission of the first TB on at least one of PUSCH resources of theuplink grant. The wireless device 3204 (e.g., the physical layer of thewireless device 3204) may cancel the transmission of the first TB on theat least one of the PUSCH resources of the uplink grant. The wirelessdevice 3204 (e.g., the HARQ entity of the wireless device 3204) maystore the first NDI value as the new NDI value. The HARQ entity of thewireless device 3204 may determine/consider that the first TB has beentransmitted by the wireless device 3204, for example, even if thewireless device 3204 has cancelled the transmission of the first TBbased on the uplink pre-emption indication 3208.

The wireless device 3204 (e.g., the physical layer of the wirelessdevice 3204) may receive second DCI 3210. The second DCI 3210 maycomprise a same HARQ process ID as the first HARQ process ID, a seconduplink grant, a RV value, and a second NDI value (e.g., 0). The physicallayer may deliver the second uplink grant and second HARQ information(e.g., the first HARQ process ID, the RV value, and/or the second NDIvalue) to a MAC layer of the wireless device 3204. The MAC entity maydeliver the uplink grant and the second HARQ information to a HARQentity of the wireless device 3204. The HARQ entity maydetermine/identify a HARQ process, for example, based on the first HARQprocess ID in the second DCI 3210. The HARQ entity may determine thatthe second NDI value is different from (e.g., toggled with respect to)to the new NDI value/the first NDI value.

The HARQ entity may instruct the HARQ process to trigger an initial (ora new) transmission of a second TB, for example, based on the second NDIvalue being different from the new NDI value/the first NDI value. TheHARQ process may instruct the physical layer to generate an initial (ora new) transmission of the second TB. The wireless device 3204 (e.g.,the physical layer of the wireless device 3204) may transmit the secondTB as the initial (or new) transmission according to the second uplinkgrant. The wireless device 3204 (e.g., the HARQ entity of the wirelessdevice 3204) may store the first NDI value as the new NDI value, forexample, before cancelling uplink transmission based on the uplinkpre-emption indication 3208. The HARQ entity may determine (e.g.,assume/consider) that the first TB has been performed by the physicallayer, for example, even if the physical layer has cancelled the uplinktransmission based on the an uplink pre-emption indication 3208. TheHARQ entity may correctly determine if an initial transmission or aretransmission is to be performed, for example, based on receiving thesecond DCI 3210 with the second NDI value and based on a comparisonbetween the second NDI value and the new NDI value. This may enablealignment between the base station 3202 and the wireless device 3204with respect to a status of an uplink HARQ process that supports anuplink pre-emption mechanism (e.g., for multiplexing differenttransmissions with different transmission formats). The alignment mayimprove system throughput, reduce data transmission latency, and/orreduce power consumption of the wireless device 3204.

FIG. 33 shows an example of an enhanced HARQ procedure. The HARQprocedure may support an uplink pre-emption indication. A base station3302 may transmit, to a wireless device 3304, first DCI 3306. The firstDCI 3306 may comprise an uplink grant and first HARQ information. Thefirst HARQ information may comprise a HARQ process ID (e.g., processID=k) and a first NDI value (e.g., 1).

The wireless device 3304 may store an NDI value (e.g., in a memory,associated with a HARQ process identified by a HARQ process ID, of thewireless device 3304). The NDI value may be associated with a HARQprocess identified by a HARQ process ID. The wireless device 3304 mayhave an initial NDI value (e.g., 0), for example, before receiving thefirst DCI 3306. The wireless device 3304 may determine that the firstNDI value (e.g., 1) is different from the initial NDI value (e.g., 0).The wireless device 3304 may determine that the first NDI is toggle withrespect to the initial NDI value. The wireless device 3304 (e.g., a HARQentity of the wireless device 3304) may obtain a MAC PDU (e.g., from amultiplexing and assembly entity of the wireless device 3304), forexample, based on the first NDI being different from the initial NDIvalue. The HARQ entity may deliver the MAC PDU, the uplink grant and thefirst HARQ information to a HARQ process identified by the HARQ processID (e.g., process ID=k). The HARQ entity may instruct the HARQ processto trigger an initial (or a new) transmission for a first TB comprisingthe MAC PDU. The HARQ process may store the MAC PDU in an associatedHARQ buffer and store the uplink grant. The HARQ process may instructthe wireless device 3304 (e.g., the physical layer of the wirelessdevice 3304) to generate an initial (or a new) transmission for thefirst TB, for example, based on the stored uplink grant. The wirelessdevice 3304 (e.g., the physical layer of the wireless device 3304) maystart the initial (or the new) transmission of the first TB on PUSCHresources, for example, based on the stored uplink grant.

The wireless device 3204 (e.g., the physical layer of the wirelessdevice 3204) may receive, from the base station, an uplink pre-emptionindication 3308, for example, if/when transmitting the first TB. Theuplink pre-emption indication 3308 may indicate that the wireless device3304 may stop/suspend/cancel) the transmission of the first TB on atleast one of the PUSCH resources. The wireless device (e.g., thephysical layer of the wireless device 3304) may stop an ongoingtransmission of the first TB on the at least one of the PUSCH resourcesof the uplink grant, for example, based on the uplink pre-emptionindication 3308. The wireless device 3304 may finish a transmission of afirst part of the first TB and may not start a transmission of a secondpart of the first TB, for example, based on the uplink pre-emptionindication 3308. The uplink pre-emption indication 3308 may indicatethat the wireless may stop/suspend/cancel the transmission of the secondpart of the first TB on the at least one of the PUSCH resources. Thewireless device 3304 (e.g., the HARQ entity of the wireless device 3304)may store the first NDI value as a new NDI value and/or store a MAC PDUassociated with the first TB. The wireless device 3304 (e.g., the HARQentity of the wireless device 3304) may determine (e.g., assume) thatthe first TB has been transmitted by the wireless device 3304, forexample, even if the wireless device 3304 has finished a transmission ofthe first part of the first TB and has stopped a transmission of thesecond part of the first TB based on the uplink pre-emption indication3308.

The wireless device 3304 (e.g., the physical layer of the wirelessdevice 3304) may receive second DCI 3310. The second DCI 3310 maycomprise a same HARQ process ID as the first HARQ process ID, a seconduplink grant, a RV value, and a second NDI value (e.g., 1). The physicallayer may deliver the second uplink grant and second HARQ information(e.g., the first HARQ process ID, the RV value, and/or the second NDIvalue) to a MAC layer of the wireless device 3304. The MAC entity maydeliver the uplink grant and the second HARQ information to a HARQentity of the wireless device. The HARQ entity may determine/identify aHARQ process, for example, based on the first HARQ process ID in thesecond DCI 3310. The HARQ entity may determine if the second NDI is thesame as/substantially the same as the new NDI value/the first NDI value.The HARQ entity may determine that the second NDI value is the sameas/substantially the same as (e.g., not toggled with respect to) the newNDI value/the first NDI value.

The HARQ entity may instruct the HARQ process to trigger aretransmission of the first TB. The HARQ process may instruct thephysical layer to generate a retransmission of the first TB. thewireless device 3304 (e.g., the physical layer of the wireless device3404) may retransmit the first TB, for example, based on the seconduplink grant. The HARQ entity may store the first NDI value as the newNDI value, for example, before stopping an ongoing uplink transmissionbased on the uplink pre-emption indication 3308. The wireless device3304 (e.g., the HARQ entity may determine (e.g., assume) that the firstTB has been transmitted by the physical layer, for example, even if thephysical layer, based on the uplink pre-emption indication 3308, hasfinished a transmission of a first part of the first TB and has notfinished a transmission of a second part of the first TB. The HARQentity may correctly determine if an initial transmission or aretransmission of the first TB is to be performed based on the storednew NDI value and the second NDI value, for example, based on thewireless device 3304 receiving the second DCI 3310 comprising the secondNDI value. This may enable alignment between the base station 3302 andthe wireless device 3304 regarding a status of an uplink HARQ processthat supports an uplink pre-emption indication (e.g., for multiplexingdifferent transmissions with different transmission formats). Thealignment may improve system throughput, reduce data transmissionlatency, and/or reduce power consumption of the wireless device 3304.

FIG. 34 shows an example of an enhanced HARQ procedure. The HARQprocedure may support an uplink pre-emption indication. A base station3402 may transmit, to a wireless device 3404, first DCI 3406. The firstDCI 3406 may comprise an uplink grant and first HARQ information. Thefirst HARQ information may comprise a HARQ process indicator/ID (e.g.,process ID=k) and a first NDI value (e.g., 1).

The wireless device 3404 may store an NDI value (e.g., in a memory,associated with a HARQ process identified by a HARQ process ID, of thewireless device 3404). The NDI value may be associated with a HARQprocess identified by a HARQ process ID. The wireless device 3404 mayhave an initial NDI value (e.g., 0), for example, before receiving thefirst DCI 3406. The wireless device 3404 may determine that the firstNDI value (e.g., 1) is different from the initial NDI value (e.g., 0).The wireless device 3404 may determine that the first NDI value istoggled with respect to the initial NDI value. The wireless device 3404(e.g., a HARQ entity of the wireless device 3404) may determine a MACPDU (e.g., from a multiplexing and assembly entity of the wirelessdevice 3404), for example, based on the first NDI value being differentfrom the initial NDI value. The HARQ entity may deliver the MAC PDU, theuplink grant and the first HARQ information to a HARQ process identifiedby the HARQ process ID (e.g., process ID=k). The HARQ entity mayinstruct the HARQ process to trigger an initial (or a new) transmissionof a first TB that comprises the MAC PDU. The HARQ process may store theMAC PDU in an associated HARQ buffer, and/or may store the uplink grant.The HARQ process may instruct the wireless device 3404 (e.g., thephysical layer of the wireless device 3404) to generate an initial (or anew) transmission of the first TB, for example, based to the storeduplink grant. The wireless device 3404 (e.g., the physical layer of thewireless device 3404) may start the initial (or the new) transmission ofthe first TB on PUSCH resources, for example, based on the stored uplinkgrant.

The wireless device 3404 (e.g., the physical layer of the wirelessdevice 3404) may receive, from the base station 3402, an uplinkpre-emption indication 3408, for example, if/when transmitting the firstTB. The uplink pre-emption indication 3408 may indicate that thewireless device 3404 may stop/suspend/cancel the transmission of thefirst TB on at least one of the PUSCH resources of the uplink grant. Thewireless device 3404 (e.g., the physical layer of the wireless device3404) may stop the ongoing transmission of the first TB on the at leastone of the PUSCH resources of the uplink grant. The wireless device 3404(e.g., the physical layer of the wireless device 3404) may finish atransmission of a first part of the first TB and may not start atransmission of a second part of the first TB, for example, based on theuplink pre-emption indication 3408. The uplink pre-emption indication3408 may indicate that the wireless may stop/suspend/cancel thetransmission of the second part of the first TB on the at least one ofthe PUSCH resources. The wireless device 3404 (e.g., a HARQ entity ofthe wireless device) may store the first NDI value as a new NDI value.The HARQ entity of the wireless device may determine/assume that thefirst TB has been transmitted by the physical layer even if the physicallayer has finished a transmission of the first part of the first TB andhas stopped a transmission of the second part of the first TB, forexample, based on the uplink pre-emption indication 3408.

The wireless device 3404 (e.g., the physical layer of the wirelessdevice 3404) may receive second DCI 3410. The second DCI 3410 maycomprise a same HARQ process ID as the first HARQ process ID, a seconduplink grant, a RV value, and a second NDI value (e.g., 0). The physicallayer may deliver the second uplink grant and second HARQ information(e.g., the first HARQ process ID, the RV value, and/or the second NDIvalue) to a MAC layer of the wireless device 3404. The MAC entity maydeliver the uplink grant and the one or more HARQ information to theHARQ entity of the wireless device 3404. The HARQ entity may identify aHARQ process, for example, based on the first HARQ process ID. The HARQentity may determine if the second NDI value is different from the newNDI value/the first NDI value. The HARQ entity may determine if thesecond NDI value is toggled with respect to the first NDI value.

The wireless device 3404 (e.g., the HARQ entity of the wireless device3404) may instruct the HARQ process to trigger an initial (or a new)transmission of a second TB, for example, based on the second NDI valuebeing different from/toggled with respect to the first NDI value/the newNDI value. The second TB may be different from the first TB. The HARQprocess may instruct the physical layer to generate an initial (or anew) transmission of the second TB. The wireless device 3404 (e.g., thephysical layer of the wireless device 3404) may transmit the second TBas the initial transmission, for example, based on the second uplinkgrant. The wireless device 3404 (e.g., the HARQ entity of the wirelessdevice 3404) may store the first NDI value before stopping an ongoinguplink transmission, for example, based on the uplink pre-emptionindication 3408. The wireless device 3404 (e.g., the HARQ entity of thewireless device 3404) may determine/assume that the first TB has beentransmitted by the physical layer, even if the physical layer hasfinished a transmission of a first part of the TB and has not finished atransmission of a second part of the TB. The wireless device 3404 maycorrectly determine whether an initial transmission or a retransmissionis to be performed based on the stored new NDI value and the second NDIvalue, for example, based on the wireless device 3404 receiving thesecond DCI 3410 that comprises the second NDI value. This may enablealignment between the base station 3402 and the wireless device 3404regarding a status of an uplink HARQ process that supports an uplinkpre-emption indication (e.g., for multiplexing different transmissionswith different transmission formats). The alignment may improve systemthroughput, reduce data transmission latency, and/or reduce powerconsumption of the wireless device 3404.

A wireless device may use a timer to monitor a channel/cell. Thewireless device may activate a timer, for example, based on receivingcontrol information. The control information may be, for example, anuplink grant. The wireless device may monitor a channel/cell, forexample, if the timer is active and running. The wireless device maystop monitoring the channel/cell and/or switch to a different channel,for example, if the timer expires.

The timer of the wireless device may expire, for example, afterreceiving an indication for cancellation of transmission. The wirelessdevice may stop monitoring the channel/cell and/or switch to a differentchannel, for example, based on the expiration of the timer. The wirelessdevice may be unable to receive a signal indicating retransmission(e.g., of the cancelled transmission) or a signal indicating anothertransmission. This may increase data transmission delay and/or reducesystem throughput.

In examples described herein, a wireless device may avoid/delayswitching to a different channel and/or stopping monitoring of a cell,for example, after the wireless device receives an indication forcancellation of transmission. The wireless device may restart a timer,for example, based on (e.g., after or in response to) receiving theindication for cancellation of transmission. This may improve datatransmission delay and/or system throughput by allowing the wirelessdevice to continue monitoring the channel/cell for a signal indicatingretransmission (e.g., of the cancelled transmission) or a signalindicating another transmission.

A wireless device may use different timers. A wireless device may starta BWP inactivity timer (e.g., bwp-InactivityTimer), for example, basedon receiving a DCI that comprises an uplink grant. The wireless devicemay keep a BWP in active state, for example, if the BWP inactivity timeris running. The wireless device may deactivate the BWP and switch to adefault BWP, for example, if the BWP inactivity timer expires.

A wireless device may start an SCell deactivation timer (e.g.,SCellDeactivationTimer), for example, based on receiving a DCI thatcomprises an uplink grant. The wireless device may keep an SCell inactive state, for example, if the SCell deactivation timer is running.The wireless device may deactivate the SCell, for example, if the SCelldeactivation timer expires.

A wireless device may start a BWP inactivity timer and/or the SCelldeactivation timer, for example, if the wireless device receives a DCIthat comprises an uplink grant. The wireless device may receive, from abase station, an uplink pre-emption indication, for example, if/when theBWP inactivity time and/or the SCell deactivation timer is running. Thewireless device may stop/cancel/suspend an uplink PUSCH transmission,for example, based on (e.g., after or in response to) receiving theuplink pre-emption indication. The uplink pre-emption indication mayindicate that the uplink PUSCH transmission may be stopped. The wirelessdevice may determine that the wireless device may receive a DCI thatindicates a retransmission, for example, if the wireless device stopsthe uplink PUSCH transmission. The BWP inactivity timer and/or the SCelldeactivation timer may expire, for example, after the wireless devicereceives the uplink pre-emption indication, and/or after the wirelessdevice determines that the wireless device may receive the DCI for theretransmission.

The wireless device may switch to the default BWP and/or deactivate theSCell, for example, based on (e.g., after or in response to) anexpiration of the BWP inactivity timer and/or an expiration of the SCelldeactivation timer. The wireless device may be unable to receive the DCIfor retransmission, for example, if the wireless device switches to thedefault BWP and/or deactivates the SCell. This may increase datatransmission delay and/or reduce system throughput.

In examples described herein, a wireless device may avoid/delayswitching to a default BWP and/or deactivating an SCell, for example,after the wireless device receives an uplink pre-emption indication. Awireless device may restart an SCell deactivation timer and/or a BWPinactivity timer, for example, based on (e.g., after or in response to)receiving the uplink pre-emption indication. This may improve datatransmission delay and/or system throughput.

FIG. 35 shows example BWP state management. A base station 3502 maytransmit, to a wireless device 3504, first DCI 3506. The first DCI maycomprise a first uplink grant. The wireless device 3504 may start a BWPinactivity timer (e.g., bwp-InactivityTimer) with an initial timervalue, for example, based on (e.g., in response to) receiving the firstDCI. The initial timer value may be indicated in an RRC message. Thewireless device 3504 may keep a first BWP in active state, for example,if the BWP inactivity timer is running. The wireless device 3504 mayperform one or more actions on the first BWP, for example, based on thefirst BWP being in active state. The wireless device 3504 operate as pera procedure described with FIG. 23 .

A timer (e.g., bwp-InactivityTimer, SCellDeactivationTimer, ordrx-InactivityTimer) may run until the timer is stopped or the timerexpires. A timer may be started, for example, if the timer is notrunning A timer may be restarted, for example, if the timer is running Atimer may be started or restarted from its initial value. A timer may bea count-down timer that counts down from a first timer value to a secondtimer value (e.g., zero). The timer may be a count-up timer that countsup from a first timer value (e.g., zero) to a second timer value. Thetimer may be a down-counter that counts down from a first counter valueto a second counter value (e.g., zero). The timer may be a count-upcounter that counts up from a first counter value (e.g., zero) to asecond counter value.

The wireless device 3504 may start an initial (or a new) transmission onPUSCH resources on the first BWP, for example, based on an uplink grantcomprised in the first DCI 3506. The wireless device 3504 may receive,from the base station 3502, an uplink pre-emption indication 3508, forexample, if/when transmitting a first TB on the PUSCH resources of theuplink grant. The uplink pre-emption indication 3508 may indicate thatthe wireless device 3504 may stop/suspend/cancel) the transmission ofthe first TB on at least one of the PUSCH resources. The wireless device3504 (e.g., the physical layer of the wireless device) may stop theongoing transmission of the first TB on the at least one of the PUSCHresources of the uplink grant, for example, based on the uplinkpre-emption indication 3508. The wireless device 3504 may finish atransmission of a first part of the first TB and may not start atransmission of a second part of the first TB, for example, based on theuplink pre-emption indication 3508. The uplink pre-emption indication3508 may indicate that the wireless device 3504 may stop/suspend/cancel)the transmission of the second part of the first TB on the at least oneof the PUSCH resources. The wireless device 3504 may restart the BWPinactivity timer, for example, based on (e.g., in response to) receivingthe uplink pre-emption indication 3508. The wireless device 3504 maymonitor a PDCCH on the first BWP, for example, if the BWP inactivitytimer is running

The wireless device 3504 may receive second DCI 3510. The second DCI maycomprise a second uplink grant. The wireless device 3504 may restart theBWP inactivity timer, and start uplink transmission based on the seconduplink grant. The uplink transmission may be a retransmission of thefirst TB or an initial transmission of a second TB. The wireless devicemay determine that the uplink transmission is the retransmission of thefirst TB or an initial transmission of a second TB, for example, basedon mechanisms described with respect to FIGS. 31-34 . Restarting the BWPinactivity timer based on receiving an uplink pre-emption indication mayavoid unnecessary BWP switching (e.g., to a default BWP). This mayimprove data transmission delay, and/or system throughput.

Various examples described herein may be used formanagement of an SCelldeactivation timer. A wireless device may start the SCell deactivationtimer with an initial value, for example, based on receiving a DCIcomprising an uplink grant on an activated SCell. The wireless devicemay start an uplink transmission on the uplink grant, for example,before receiving an uplink pre-emption indication. The wireless devicemay stop an ongoing uplink transmission on the uplink grant, forexample, based on (e.g., in response to) receiving the uplinkpre-emption indication. The wireless device may restart the SCelldeactivation timer, for example, based on (e.g., in response to)receiving the uplink pre-emption indication. The wireless device maykeep the SCell in active state, for example, if the SCell deactivationtimer is running. The wireless device may monitor a PDCCH on (or for)the SCell to detect second DCI for a second uplink grant. The wirelessdevice may perform an uplink transmission on the second uplink grant,for example, based on receiving the second uplink grant. Restarting theSCell deactivation timer based on receiving an uplink pre-emptionindication, may avoid unnecessary SCell deactivation. This may improvedata transmission delay, and/or system throughput.

FIG. 36 shows example of BWP state management. A base station 3602 maytransmit, to a wireless device (3604, first DCI 3606. The first DCI 3606may comprise a first uplink grant. The wireless device 3604 may start aBWP inactivity timer (e.g., bwp-InactivityTimer) with an initial timervalue, for example, based on (e.g., in response to) receiving the firstDCI. The initial timer value may be indicated in an RRC message. Thewireless device 3604 may keep a first BWP in active state, for example,if the BWP inactivity timer is running.

The wireless device 3604 may receive, from the base station 3602, anuplink pre-emption indication 3608, for example, before the wirelessdevice starts a transmission of a first TB on PUSCH resources of theuplink grant. The uplink pre-emption indication 3608 may indicate thatthe wireless device 3604 may cancel/suspend/stop a scheduledtransmission of the first TB on at least one of the PUSCH resources. Thewireless device 3604 (e.g., the physical layer of the wireless device3604) may cancel the scheduled transmission of the first TB on the atleast one of the PUSCH resources of the uplink grant, for example, basedon (e.g., in response to) the uplink pre-emption indication 3608. Thewireless device 3604 may restart the BWP inactivity timer, for example,based on (e.g., in response to) receiving the uplink pre-emptionindication. The wireless device 3604 may monitor a PDCCH on the firstBWP, for example, if the BWP inactivity timer is running

The wireless device 3604 may receive second DCI comprising a seconduplink grant. The wireless device 3604 may restart the BWP inactivitytimer, and start uplink transmission based on the second uplink grant.The uplink transmission may be a transmission of the first TB or atransmission of a second TB. The wireless device 3604 may determine thatthe uplink transmission is the transmission of the first TB or aninitial transmission of a second TB, for example, based on mechanismsdescribed with respect to FIGS. 31-34 . Restarting the BWP inactivitytimer based on receiving an uplink pre-emption indication may avoidunnecessary BWP switching (e.g., to a default BWP). This may improvedata transmission delay, and/or system throughput.

Various examples described herein may be used for management of an SCelldeactivation timer. A wireless device may start the SCell deactivationtimer with an initial value, for example, based on (e.g., in responseto) receiving a DCI comprising an uplink grant on an activated SCell.The wireless device may receive an uplink pre-emption indication, forexample, before the wireless device starts an uplink transmission on theuplink grant. The wireless device may cancel the scheduled (e.g.,future) uplink transmission on the uplink grant, for example, based on(e.g., in response to) receiving the uplink pre-emption indication. Thewireless device may restart the SCell deactivation timer, for example,based on (e.g., in response to) receiving the uplink pre-emptionindication. The wireless device may keep the SCell in active state, forexample, if the SCell deactivation timer is running. The wireless devicemay monitor a PDCCH on (or for) the SCell to detect second DCI for asecond uplink grant. The wireless device may perform uplink transmissionon the second uplink grant, for example, based on receiving the seconduplink grant. Restarting the SCell deactivation timer based on receivingan uplink pre-emption indication may avoid unnecessary SCelldeactivation. This may improve data transmission delay, and/or systemthroughput.

A wireless device, configured with a DRX operation, may start a DRXinactivity timer (e.g., drx-InactivityTimer), for example, if thewireless device receives DCI comprising an uplink grant. The wirelessdevice may stay in a DRX active state, for example, if the DRXinactivity timer is running. The wireless device may monitor PDCCHand/or receive data packet on PDSCH, for example, if the wireless deviceis in a DRX active state. The wireless device may switch to a DRXoff/sleep mode (e.g., not in DRX active state), for example, based on anexpiration of the DRX inactivity timer. The wireless device may stopmonitoring PDCCH and/or stop receiving data packet on PDSCH, forexample, if the wireless device is in a DRX off/sleep mode. This mayreduce power consumption. The wireless device may start an uplinktransmission, for example, based on the uplink grant. The wirelessdevice may receive an uplink grant, for example, before receiving anuplink pre-emption indication. The wireless device may stop an ongoinguplink transmission, for example, based on (e.g., in response to) theuplink pre-emption indication. The wireless device may expect to receivesecond DCI for uplink retransmission. The DRX inactivity timer mayexpires, for example, after the wireless device receives the uplinkpre-emption indication, and/or if the wireless device is expecting toreceive the second DCI for the retransmission. The wireless device mayswitch to the DRX off/sleep mode, for example, based on (e.g., inresponse to) an expiration of the DRX inactivity timer. This mayincrease data transmission delay, and/or reduce system throughput.

A wireless device may avoid/delay switching to a DRX off/sleep mode, forexample, after the wireless device receives an uplink pre-emptionindication. The wireless device may restart a DRX inactivity timer, forexample, based on (e.g., after or in response to) receiving an uplinkpre-emption indication. This may improve data transmission delay and/orsystem throughput.

FIG. 37 shows example DRX operation. A base station 3702 may transmit toa wireless device 3704 one or more RRC messages 3706. The one or RRCmessages 3706 may comprise configuration parameters of a DRX operation.The wireless device 3704 may activate the DRX operation based on theconfiguration parameters. The wireless device 3704 may implement, forexample, one or examples described with reference to FIG. 24 and/or FIG.25 . The base station 3702 may transmit, to the wireless device 3704,first DCI 3708. The first DCI 3708 may comprise a first uplink grant.The wireless device 3704 may start a DRX inactivity timer (e.g.,drx-InactivityTimer) with an initial timer value, for example, based onreceiving the first DCI 3708. The initial timer value may be indicatedin an RRC message. The wireless device 3704 may be in a DRX activestate, for example, if the DRX inactivity timer is running

The wireless device 3704 may start an initial (or a new) transmission onPUSCH resources (e.g., on an active BWP and/or an active cell), forexample, based on an uplink grant comprised in the first DCI 3708. Thewireless device 3704 may receive, from the base station 3702, an uplinkpre-emption indication 3710, for example, if/when transmissioning afirst TB on PUSCH resources of the uplink grant. The uplink pre-emptionindication 3710 may indicate that the wireless device 3704 maystop/suspend/cancel the transmission of the first TB on at least one ofthe PUSCH resources. The wireless device 3704 (e.g., a physical layer ofthe wireless device 3704) may stop an ongoing transmission of the firstTB on the at least one of the PUSCH resources of the uplink grant, forexample, based on (e.g., in response to) the uplink pre-emptionindication 3710. The wireless device 3704 may finish a transmission of afirst part of the first TB and may not start a transmission of a secondpart of the first TB, for example, based on the uplink pre-emptionindication. The uplink pre-emption indication 3710 may indicate that thewireless may stop/suspend/cancel the transmission of the second part ofthe first TB on the at least one of the PUSCH resources. The wirelessdevice 3704 may restart the DRX inactivity timer, for example, based onreceiving the uplink pre-emption indication 3710. The wireless device3704 may monitor a PDCCH on the active BWP and/or the active cell, forexample, if the DRX inactivity timer is running.

The wireless device 3704 may receive second DCI comprising a seconduplink grant. The wireless device may restart the DRX inactivity timer,and/or start uplink transmission based on the second uplink grant. Theuplink transmission may be a retransmission of the first TB or aninitial transmission of a second TB. The wireless device may determinethat the uplink transmission is the retransmission of the first TB or aninitial transmission of a second TB, for example, based on mechanismsdescribed with respect to FIGS. 31-34 . Restarting the DRX inactivitytimer based on receiving an uplink pre-emption indication may avoidunnecessary switching from a DRX active state to DRX off/sleepmode/state. This may improve data transmission delay, and/or systemthroughput.

A wireless device may receive first DCI. The first DCI may indicatefirst uplink radio resources, a first HARQ process ID, and/or a firstNDI value. The first uplink radio resources may comprise first uplinktime/frequency resources and/or at least second uplink time/frequencyresources. The wireless device may generate a first TB based on thefirst DCI. The wireless device may receive second DCI indicating thatthe first uplink time/frequency resources are pre-empted. The second DCImay be a group command DCI that is addressed to a group of wirelessdevices comprising the wireless device. The second DCI may be a wirelessdevice-specific DCI addressed to the wireless device. The wirelessdevice (e.g., a physical layer of the wireless device) may drop atransmission of the first TB on the first uplink time/frequencyresources, for example, based on (e.g., in response to) the second DCI.The wireless device (e.g., the physical layer of the wireless device)may drop the transmission of the first TB on the first uplinktime/frequency resources and/or the at least second uplinktime/frequency resources. The wireless device (e.g., a MAC entity of thewireless device) may determine/assume that the first TB has beentransmitted, even if the physical layer has dropped the transmission ofthe first TB based on the second DCI. The wireless device (e.g., the MACentity of the wireless device) may store the first NDI value received inthe first DCI and/or store a MAC PDU associated with the first TB, forexample, if the physical layer has dropped the transmission of the firstTB. The wireless device may store the first NDI value received in thefirst DCI, for example, if the physical layer does not drop thetransmission of the first TB in response to the second DCI. The wirelessdevice may receive third DCI. The third DCI may comprise second uplinkradio resources, a same HARQ process ID as the first HARQ process ID,and/or a second NDI value. The wireless device may determine if thesecond NDI value is different from the stored NDI value/the first NDIvalue. The wireless device may determine if the second NDI value istoggled with respect to the stored NDI value/the first NDI value. Thewireless device may determine that the second NDI value is toggled, forexample, based on the second NDI value being different from the storedNDI value/the first NDI value. The wireless device may determine thatthe second NDI value is not toggled, for example, based on the secondNDI value being same as the stored NDI value/the first NDI value. Thewireless device may retransmit the first TB based on the second uplinkradio resources, for example, if the second NDI value is not toggled.The wireless device may transmit a second TB based on the second uplinkradio resources, for example, if the second NDI value is toggled.

A wireless device may receive first DCI. The first DCI may indicatefirst uplink radio resources, a first HARQ process ID, and/or a firstNDI value. The first uplink radio resources may comprise first uplinktime/frequency resources and/or at least second uplink time/frequencyresources. The wireless device may generate a first TB based on thefirst DCI. The wireless device may start a transmission of the first TBon the first uplink radio resources. The wireless device may receivesecond DCI indicating the first uplink time/frequency resources arepre-empted. The wireless device may receive the second DCI, for example,if/when the wireless device is transmitting the first TB on the firstuplink radio resources. The wireless device (e.g., a physical layer ofthe wireless device) may drop an ongoing transmission of the first TB atleast on the first uplink time/frequency resources, for example, basedon (e.g., after or in response to) the second DCI. The wireless devicemay drop the ongoing transmission of the first TB on the first uplinktime/frequency resources and the at least second uplink time/frequencyresources, for example, based on (e.g., in response to) the second DCI.The wireless device (e.g., a MAC entity of the wireless device) maydetermine/assume that the first TB has been transmitted of the first TB,even if the physical layer has dropped the ongoing transmission of thefirst TB based on the second DCI. The wireless device (e.g., the MACentity of the wireless device) may store the first NDI value received inthe first DCI and/or store the first TB in a HARQ buffer associated witha HARQ process identified by the first HARQ process ID, for example, ifthe physical layer has dropped the ongoing transmission of the first TB.The wireless device (e.g., the MAC entity of the wireless device) maystore the first NDI value received in the first DCI, for example, if thephysical layer does not drop the ongoing transmission of the first TBbased on the second DCI. The wireless device may receive a third DCI.The third DCI may comprise second uplink radio resources, a same HARQprocess ID as the first HARQ process ID, and/or a second NDI value. Thewireless device may determine if the second NDI value is different fromthe stored NDI value/the first NDI value. The wireless device maydetermine if the second NDI value is toggled with respect to the storedNDI value/the first NDI value. The wireless device may determine thatthe second NDI value is toggled, for example, based on the second NDIvalue being different from the stored NDI value/the first NDI value. Thewireless device may determine that the NDI is not toggled, for example,based on the second NDI value being same as the stored NDI value/thefirst NDI value. The wireless device may retransmit the first TB on thesecond uplink radio resources, for example, if the NDI is not toggled.The wireless device may transmit a second TB on the second uplink radioresources, for example, if the NDI is toggled.

A wireless device may receive first DCI comprising a first uplink grant.The wireless device may start (or restart) a BWP inactivity timer withan initial timer value, for example, based on (e.g., after or inresponse to) receiving the first DCI. The wireless device may receivesecond DCI. The second DCI may comprise an uplink pre-emption indicationon an uplink radio resource. The uplink radio resource may overlap withone or more uplink radio resources of the first uplink grant. Thewireless device may drop a transmission of a first TB on the uplinkradio resource and/or start (or restart) the BWP inactivity timer, forexample, based on the uplink pre-emption indication indicating that theuplink radio resource is pre-empted. The wireless device may monitor aPDCCH for a third DCI, for example, if the BWP inactivity timer isrunning. The wireless device may transmit a second TB or retransmit thefirst TB, for example, based on receiving the third DCI.

A wireless device may receive first DCI comprising a first uplink grant.The wireless device may start (or restart) a SCell deactivation timerwith an initial timer value, for example, based on (e.g., after or inresponse to) receiving the first DCI. The wireless device may receivesecond DCI. The second DCI may comprise an uplink pre-emption indicationon an uplink radio resource. The uplink radio resource may overlap withone or more uplink radio resources of the first uplink grant. Thewireless device may drop a transmission of a first TB on the uplinkradio resource and/or start (or restart) the SCell deactivation timer,for example, based on the uplink pre-emption indication indicating thatthe uplink radio resource is pre-empted. The wireless device may monitora PDCCH for a third DCI, for example, if the SCell deactivation timer isrunning. The wireless device may transmit a second TB or retransmit thefirst TB, for example, based on receiving the third DCI.

A wireless device may receive first DCI comprising a first uplink grant.The wireless device may start (or restart) a DRX inactivity timer withan initial timer value, for example, based on (e.g., after or inresponse to) receiving the first DCI. The wireless device may receivesecond DCI. The second DCI may comprise an uplink pre-emption indicationon an uplink radio resource. The uplink radio resource may overlap withone or more uplink radio resource of the first uplink grant. Thewireless device may drop a transmission of a first TB on the uplinkradio resource and/or start (or restart) the DRX inactivity timer, forexample, based on the uplink pre-emption indication indicating that theuplink radio resource is pre-empted. The wireless device may monitor aPDCCH for a third DCI, for example, if the DRX inactivity timer isrunning. The wireless device may transmit a second TB or retransmit thefirst TB, for example, based on the third DCI.

FIG. 38 shows an example method for an enhanced HARQ operation. At step3804, a wireless device may receive (e.g., from a base station) firstDCI. The first DCI may comprise an uplink radio resource, a HARQ ID, anda first NDI. At step 3808, the wireless device may receive second DCI.The second DCI may indicate that the uplink radio resource ispre-empted. At step 3812, the wireless device may cancel a transmissionof a data unit, via the uplink radio resource, for example, based ondetecting that the uplink radio resource is pre-empted. At step 3816,the wireless device may store the data unit in a buffer and/or store thefirst NDI. The buffer may be associated with a HARQ process that isidentified by the HARQ ID. At step 3820, the wireless device maytransmit the data unit based on receiving third DCI comprising the HARQID and a second NDI, wherein the second NDI is not toggled compared tothe first NDI.

A wireless device may perform a method comprising multiple operations.The wireless device may receive first DCI that indicates: an uplinkradio resource; a HARQ identifier; and a first NDI. The wireless devicemay receive second DCI that indicates that the uplink radio resource ispre-empted. The wireless device may, based on detecting that the uplinkradio resource is pre-empted, cancel a transmission, via the uplinkradio resource, of a MAC packet. The wireless device may transmit, basedon receiving third DCI comprising the HARQ identifier and a second NDI,the MAC packet, wherein the second NDI is not toggled compared to thefirst NDI.

The wireless device may also perform one or more additional operations.The wireless device may store the MAC packet in a buffer associated witha HARQ process indicated by the HARQ identifier. The wireless device mayreceive fourth DCI. The wireless device may transmit, based on the thirdNDI being toggled compared to the second NDI, a second MAC packet. Thefirst NDI may have a length of one bit. The wireless device may storethe first NDI. The wireless device may determine that the second NDI isnot toggled compared to first NDI based on the second NDI being same asstored first NDI. The cancelling the transmission of MAC packet maycomprise transmitting, via the uplink radio resource and based onreceiving the first DCI, a first portion of the MAC packet. Thecancelling the transmission of the data unit may comprise dropping ascheduled transmission, via the uplink radio resource, of a secondportion of the MAC packet. The wireless device may receive one or moreradio resource control messages comprising configuration parameters,wherein the configuration parameters indicate an association between oneor more pre-emption indicators and one or more uplink radio resources,and wherein the one or more uplink radio resources comprises the uplinkradio resource. The second DCI may comprise the one or more pre-emptionindicators, wherein a pre-emption indicator, of the one or morepre-emption indicators and associated with the uplink radio resource,indicates cancellation of a transmission of the MAC packet via theuplink radio resource. Based on the association, a pre-emption indicatorof the one or more pre-emption indicators, corresponding to anassociated uplink radio resource of the one or more uplink radioresources, may indicate whether the associated uplink radio resources ispre-empted. The uplink radio resource may comprise at least one of: anumber of symbols; a number of resource blocks; or a number ofdemodulation reference signal ports. The uplink radio resource beingpre-empted may comprise that transmission by the wireless device on theuplink radio resource is not allowed. The second DCI may comprise: agroup common DCI addressed to a group of wireless devices comprising thewireless device, or a wireless device-specific DCI dedicatedly addressedto the wireless device. The wireless device may receive the second DCIbased on cyclic redundancy check (CRC) bits of the second DCI beingscrambled by a radio network temporary identifier (RNTI) dedicated forpre-emption indication.

Systems, devices and media may be configured with the method. Acomputing device may comprise one or more processors; and memory storinginstructions that, when executed, cause the computing device to performthe described method, additional operations and/or include theadditional elements. A system may comprise a first computing deviceconfigured to perform the described method, additional operations and/orinclude the additional elements; and a second computing deviceconfigured to send the first DCI. A computer-readable medium may storeinstructions that, when executed, cause performance of the describedmethod, additional operations and/or include the additional elements.

A wireless device may perform a method comprising multiple operations.The wireless device may receive first DCI that indicates an uplink radioresource and a first NDI. The wireless device may receive second DCIthat indicates that the uplink radio resource is pre-empted. Thewireless device may, based on detecting that the uplink radio resourceis pre-empted, cancel a transmission, via the uplink radio resource, ofa first transport block. The wireless device may receive third DCI thatindicates a second NDI. The wireless device may transmit, based on thesecond NDI being toggled compared to the first NDI, a second transportblock.

The wireless device may also perform one or more additional operations.The wireless device may start an inactivity timer. The wireless devicemay restart, based on the cancelling the transmission of the first dataunit, the inactivity timer. The wireless device may monitor, based onthe inactivity timer, a physical downlink control channel (PDCCH),wherein the receiving third DCI is based on the monitoring the PDCCH.The first NDI may have a length of one bit. The wireless device maystore the first NDI. The cancelling the transmission of the data unitmay comprise transmitting, via the uplink radio resource and based onreceiving the first DCI, a first portion of the data unit. Thecancelling the transmission of the data unit may comprise dropping atransmission of a second portion of the data unit via the uplink radioresource. The wireless device may receive one or more radio resourcecontrol messages comprising configuration parameters, wherein theconfiguration parameters indicate an association between one or morepre-emption indicators and one or more radio uplink resources, andwherein the one or more uplink radio resources comprises the uplinkradio resource. The second DCI may comprise the one or more pre-emptionindicators, wherein a pre-emption indicator, of the one or morepre-emption indicators and associated with the uplink radio resourceindicates cancellation of a transmission of the first data unit via theuplink radio resource. The wireless device may receive fourth DCI thatindicates the uplink radio resource and a third NDI. The wireless devicemay receive fifth DCI that indicates that the uplink radio resource ispre-empted. The wireless device may, based on detecting that the uplinkradio resource is pre-empted, cancel a transmission, via the uplinkradio resource, of a third transport block. The wireless device mayreceive sixth DCI, wherein the sixth DCI indicates a fourth NDI. Thewireless device may transmit, based on the fourth NDI not being toggledcompared to the third NDI, the third transport block.

Systems, devices and media may be configured with the method. Acomputing device may comprise one or more processors; and memory storinginstructions that, when executed, cause the computing device to performthe described method, additional operations and/or include theadditional elements. A system may comprise a first computing deviceconfigured to perform the described method, additional operations and/orinclude the additional elements; and a second computing deviceconfigured to send the first DCI. A computer-readable medium may storeinstructions that, when executed, cause performance of the describedmethod, additional operations and/or include the additional elements.

A wireless device may perform a method comprising multiple operations.The wireless device may receive first DCI that indicates an uplink radioresource. The wireless device may start an inactivity timer. Thewireless device may receive second DCI that indicates that the uplinkradio resource is pre-empted. The wireless device may, based ondetecting that the uplink radio resource is pre-empted, cancel atransmission, via the uplink radio resource, of a first transport block.The wireless device may restart, based on the cancelling thetransmission, the inactivity timer. The wireless device may receive,after restarting the inactivity timer, third DCI.

The wireless device may also perform one or more additional operations.The wireless device may, based on the inactivity timer, monitor a PDCCH.The inactivity timer may be at least one of a bandwidth part BWPinactivity timer or a DRX inactivity timer. The first DCI may indicate aHARQ identifier and a first NDI, and the third DCI may indicate the HARQidentifier and a second NDI. The wireless device may store the firsttransport block in a buffer of a HARQ process indicated by the HARQidentifier. The wireless device may transmit the first transport blockbased on determining that the second NDI is not toggled compared to thefirst NDI. The wireless device may transmit a second transport blockbased on determining that the second NDI is toggled compared to thefirst NDI. The cancelling the transmission of the first transport blockmay comprise transmitting, via the uplink radio resource and based onreceiving the first DCI, a first portion of the first transport block.The cancelling the transmission of the first transport block maycomprise dropping a scheduled transmission, via the uplink radioresource, of a second portion of the first transport block.

Systems, devices and media may be configured with the method. Acomputing device may comprise one or more processors; and memory storinginstructions that, when executed, cause the computing device to performthe described method, additional operations and/or include theadditional elements. A system may comprise a first computing deviceconfigured to perform the described method, additional operations and/orinclude the additional elements; and a second computing deviceconfigured to send the first DCI. A computer-readable medium may storeinstructions that, when executed, cause performance of the describedmethod, additional operations and/or include the additional elements.

A wireless device may receive first DCI comprising a radio resource andan NDI. The wireless device may receive second DCI indicating that theradio resource is pre-empted. The wireless device may, based ondetecting that the uplink radio resource is pre-empted, cancel atransmission of a transport block on the uplink radio resource. Thewireless device may receive a third DCI comprising a second NDI. Thewireless device may transmit the transport block based on the second NDInot being toggled compared to the first NDI.

A wireless device may receive first DCI indicating: a first uplink radioresource; a first HARQ identifier; and a first NDI. The wireless devicemay receive receiving second DCI indicating that the first uplink radioresource is pre-empted. The wireless device may cancel, in response tothe second DCI indicating that the first uplink radio resource ispre-empted, a transmission of a first transport block on the firstuplink radio resource. The wireless device may determine, based on thecancelling the transmission, that the transmission of the firsttransport block has been performed. The wireless device may store, basedon the determining that the transmission of the first transport block isperformed and the cancelling the transmission, at least one of: a valueof the first NDI; and a MAC PDU in a HARQ buffer of a HARQ processidentified by the first HARQ identifier.

A wireless device may perform a method comprising multiple operations.The wireless device may receive first DCI. The first DCI may indicate:an uplink radio resource; a HARQ identifier; and a first NDI. Thewireless device may receive second DCI, wherein the second DCI indicatesthat the uplink radio resource is pre-empted. The wireless device may,based on detecting that the radio resource is pre-empted, cancelling atransmission, via the uplink radio resource, of a data unit. Thewireless device may, based on the cancelling the transmission,considering that the transmission of the data unit has been performed.The wireless device may transmit the data unit, based on receiving thirdDCI.

FIG. 39 shows example elements of a computing device that may be used toimplement any of the various devices described herein, including, e.g.,the base station 120A and/or 120B, the wireless device 110 (e.g., 110Aand/or 110B), or any other base station, wireless device, or computingdevice described herein. The computing device 3900 may include one ormore processors 3901, which may execute instructions stored in therandom-access memory (RAM) 3903, the removable media 3904 (such as aUniversal Serial Bus (USB) drive, compact disk (CD) or digital versatiledisk (DVD), or floppy disk drive), or any other desired storage medium.Instructions may also be stored in an attached (or internal) hard drive3905. The computing device 3900 may also include a security processor(not shown), which may execute instructions of one or more computerprograms to monitor the processes executing on the processor 3901 andany process that requests access to any hardware and/or softwarecomponents of the computing device 3900 (e.g., ROM 3902, RAM 3903, theremovable media 3904, the hard drive 3905, the device controller 3907, anetwork interface 3909, a GPS 3911, a Bluetooth interface 3912, a WiFiinterface 3913, etc.). The computing device 3900 may include one or moreoutput devices, such as the display 3906 (e.g., a screen, a displaydevice, a monitor, a television, etc.), and may include one or moreoutput device controllers 3907, such as a video processor. There mayalso be one or more user input devices 3908, such as a remote control,keyboard, mouse, touch screen, microphone, etc. The computing device3900 may also include one or more network interfaces, such as a networkinterface 3909, which may be a wired interface, a wireless interface, ora combination of the two. The network interface 3909 may provide aninterface for the computing device 3900 to communicate with a network3910 (e.g., a RAN, or any other network). The network interface 3909 mayinclude a modem (e.g., a cable modem), and the external network 3910 mayinclude communication links, an external network, an in-home network, aprovider's wireless, coaxial, fiber, or hybrid fiber/coaxialdistribution system (e.g., a DOCSIS network), or any other desirednetwork. Additionally, the computing device 3900 may include alocation-detecting device, such as a global positioning system (GPS)microprocessor 3911, which may be configured to receive and processglobal positioning signals and determine, with possible assistance froman external server and antenna, a geographic position of the computingdevice 3900.

The example in FIG. 39 may be a hardware configuration, although thecomponents shown may be implemented as software as well. Modificationsmay be made to add, remove, combine, divide, etc. components of thecomputing device 3900 as desired. Additionally, the components may beimplemented using basic computing devices and components, and the samecomponents (e.g., processor 3901, ROM storage 3902, display 3906, etc.)may be used to implement any of the other computing devices andcomponents described herein. For example, the various componentsdescribed herein may be implemented using computing devices havingcomponents such as a processor executing computer-executableinstructions stored on a computer-readable medium, as shown in FIG. 39 .Some or all of the entities described herein may be software based, andmay co-exist in a common physical platform (e.g., a requesting entitymay be a separate software process and program from a dependent entity,both of which may be executed as software on a common computing device).

The disclosed mechanisms herein may be performed if certain criteria aremet, for example, in a wireless device, a base station, a radioenvironment, a network, a combination of the above, and/or the like.Example criteria may be based on, for example, wireless device and/ornetwork node configurations, traffic load, initial system set up, packetsizes, traffic characteristics, a combination of the above, and/or thelike. If the one or more criteria are met, various examples may be used.It may be possible to implement examples that selectively implementdisclosed protocols.

A base station may communicate with a mix of wireless devices. Wirelessdevices and/or base stations may support multiple technologies, and/ormultiple releases of the same technology. Wireless devices may have somespecific capability(ies) depending on wireless device category and/orcapability(ies). A base station may comprise multiple sectors. A basestation communicating with a plurality of wireless devices may refer tobase station communicating with a subset of the total wireless devicesin a coverage area. Wireless devices referred to herein may correspondto a plurality of wireless devices of a particular LTE or 5G releasewith a given capability and in a given sector of a base station. Aplurality of wireless devices may refer to a selected plurality ofwireless devices, and/or a subset of total wireless devices in acoverage area. Such devices may operate, function, and/or perform basedon or according to drawings and/or descriptions herein, and/or the like.There may be a plurality of base stations or a plurality of wirelessdevices in a coverage area that may not comply with the disclosedmethods, for example, because those wireless devices and/or basestations perform based on older releases of LTE or 5G technology.

One or more features described herein may be implemented in acomputer-usable data and/or computer-executable instructions, such as inone or more program modules, executed by one or more computers or otherdevices. Generally, program modules include routines, programs, objects,components, data structures, etc. that perform particular tasks orimplement particular abstract data types when executed by a processor ina computer or other data processing device. The computer executableinstructions may be stored on one or more computer readable media suchas a hard disk, optical disk, removable storage media, solid statememory, RAM, etc. The functionality of the program modules may becombined or distributed as desired. The functionality may be implementedin whole or in part in firmware or hardware equivalents such asintegrated circuits, field programmable gate arrays (FPGA), and thelike. Particular data structures may be used to more effectivelyimplement one or more features described herein, and such datastructures are contemplated within the scope of computer executableinstructions and computer-usable data described herein.

Many of the elements in examples may be implemented as modules. A modulemay be an isolatable element that performs a defined function and has adefined interface to other elements. The modules may be implemented inhardware, software in combination with hardware, firmware, wetware(i.e., hardware with a biological element) or a combination thereof, allof which may be behaviorally equivalent. For example, modules may beimplemented as a software routine written in a computer languageconfigured to be executed by a hardware machine (such as C, C++,Fortran, Java, Basic, Matlab or the like) or a modeling/simulationprogram such as Simulink, Stateflow, GNU Octave, or Lab VIEWMathScript.Additionally or alternatively, it may be possible to implement modulesusing physical hardware that incorporates discrete or programmableanalog, digital and/or quantum hardware. Examples of programmablehardware may comprise: computers, microcontrollers, microprocessors,application-specific integrated circuits (ASICs); field programmablegate arrays (FPGAs); and complex programmable logic devices (CPLDs).Computers, microcontrollers, and microprocessors may be programmed usinglanguages such as assembly, C, C++ or the like. FPGAs, ASICs, and CPLDsmay be programmed using hardware description languages (HDL), such asVHSIC hardware description language (VHDL) or Verilog, which mayconfigure connections between internal hardware modules with lesserfunctionality on a programmable device. The above-mentioned technologiesmay be used in combination to achieve the result of a functional module.

A non-transitory tangible computer readable media may compriseinstructions executable by one or more processors configured to causeoperations of multi-carrier communications described herein. An articleof manufacture may comprise a non-transitory tangible computer readablemachine-accessible medium having instructions encoded thereon forenabling programmable hardware to cause a device (e.g., a wirelessdevice, wireless communicator, a wireless device, a base station, andthe like) to allow operation of multi-carrier communications describedherein. The device, or one or more devices such as in a system, mayinclude one or more processors, memory, interfaces, and/or the like.Other examples may comprise communication networks comprising devicessuch as base stations, wireless devices or user equipment (wirelessdevice), servers, switches, antennas, and/or the like. A network maycomprise any wireless technology, including but not limited to,cellular, wireless, WiFi, 4G, 5G, any generation of 3GPP or othercellular standard or recommendation, wireless local area networks,wireless personal area networks, wireless ad hoc networks, wirelessmetropolitan area networks, wireless wide area networks, global areanetworks, space networks, and any other network using wirelesscommunications. Any device (e.g., a wireless device, a base station, orany other device) or combination of devices may be used to perform anycombination of one or more of steps described herein, including, forexample, any complementary step or steps of one or more of the abovesteps.

Although examples are described above, features and/or steps of thoseexamples may be combined, divided, omitted, rearranged, revised, and/oraugmented in any desired manner Various alterations, modifications, andimprovements will readily occur to those skilled in the art. Suchalterations, modifications, and improvements are intended to be part ofthis description, though not expressly stated herein, and are intendedto be within the spirit and scope of the descriptions herein.Accordingly, the foregoing description is by way of example only, and isnot limiting.

The invention claimed is:
 1. A method comprising: receiving, by awireless device, first downlink control information (DCI) thatindicates: an uplink radio resource; and a first new data indicator(NDI); receiving second DCI that indicates that the uplink radioresource is pre-empted; based on detecting that the uplink radioresource is pre-empted, cancelling an uplink transmission associatedwith the uplink radio resource; and based on the cancelling the uplinktransmission and based on a comparison of the first NDI to a second NDIreceived via third DCI, transmitting one of: a first media accesscontrol (MAC) packet corresponding to the uplink transmission, or asecond MAC packet.
 2. The method of claim 1, further comprising:transmitting the first MAC packet based on a result of the comparison ofthe first NDI to the second NDI indicating at least one of: the secondNDI and the first NDI having a same value, or a value of the second NDInot being toggled compared to a value of the first NDI.
 3. The method ofclaim 1, further comprising: transmitting the second MAC packet based ona result of the comparison of the first NDI to the second NDI indicatingat least one of: the second NDI and the first NDI not having a samevalue, or a value of the second NDI being toggled compared to a value ofthe first NDI.
 4. The method of claim 1, further comprising: storing thefirst MAC packet in a buffer associated with a hybrid automatic repeatrequest (HARQ) process indicated by a HARQ identifier.
 5. The method ofclaim 1, wherein the cancelling the uplink transmission comprises:transmitting, via the uplink radio resource and based on receiving thefirst DCI, a first portion of the first MAC packet; and dropping ascheduled transmission, via the uplink radio resource, of a secondportion of the first MAC packet.
 6. The method of claim 1, wherein thecancelling the uplink transmission comprises cancelling a transmissionassociated with the first NDI.
 7. The method of claim 1, wherein theuplink transmission comprises a physical uplink shared channel (PUSCH)transmission.
 8. The method of claim 1, wherein: the first DCI furtherindicates a hybrid automatic repeat request (HARQ) identifier, and thethird DCI indicates the HARQ identifier.
 9. A wireless devicecomprising: one or more processors; and memory storing instructionsthat, when executed by the one or more processors, cause the wirelessdevice to: receive first downlink control information (DCI) thatindicates: an uplink radio resource; and a first new data indicator(NDI); receive second DCI that indicates that the uplink radio resourceis pre-empted; based on detecting that the uplink radio resource ispre-empted, cancel an uplink transmission associated with the uplinkradio resource; and based on cancelling the uplink transmission andbased on a comparison of the first NDI to a second NDI received viathird DCI, transmit one of: a first media access control (MAC) packetcorresponding to the uplink transmission, or a second MAC packet. 10.The wireless device of claim 9, wherein the instructions, when executedby the one or more processors, cause the wireless device to: transmitthe first MAC packet based on a result of the comparison of the firstNDI to the second NDI indicating at least one of: the second NDI and thefirst NDI having a same value, or a value of the second NDI not beingtoggled compared to a value of the first NDI.
 11. The wireless device ofclaim 9, wherein the instructions, when executed by the one or moreprocessors, cause the wireless device to: transmit the second MAC packetbased on a result of the comparison of the first NDI to the second NDIindicating at least one of: the second NDI and the first NDI not havinga same value, or a value of the second NDI being toggled compared to avalue of the first NDI.
 12. The wireless device of claim 9, wherein theinstructions, when executed by the one or more processors, cause thewireless device to: store the first MAC packet in a buffer associatedwith a hybrid automatic repeat request (HARQ) process indicated by aHARQ identifier.
 13. The wireless device of claim 9, wherein theinstructions, when executed by the one or more processors, cause thewireless device to cancel the uplink transmission by: transmitting, viathe uplink radio resource and based on receiving the first DCI, a firstportion of the first MAC packet; and dropping a scheduled transmission,via the uplink radio resource, of a second portion of the first MACpacket.
 14. The wireless device of claim 9, wherein the instructions,when executed by the one or more processors, cause the wireless deviceto cancel the uplink transmission by cancelling a transmissionassociated with the first NDI.
 15. The wireless device of claim 9,wherein the uplink transmission comprises a physical uplink sharedchannel (PUSCH) transmission.
 16. The wireless device of claim 9,wherein: the first DCI further indicates a hybrid automatic repeatrequest (HARQ) identifier, and the third DCI indicates the HARQidentifier.
 17. A non-transitory computer-readable medium storinginstructions that, when executed, cause a wireless device to: receivefirst downlink control information (DCI) that indicates: an uplink radioresource; and a first new data indicator (NDI); receive second DCI thatindicates that the uplink radio resource is pre-empted; based ondetecting that the uplink radio resource is pre-empted, cancel an uplinktransmission associated with the uplink radio resource; and based oncancelling the uplink transmission and based on a comparison of thefirst NDI to a second NDI received via third DCI, transmit one of: afirst media access control (MAC) packet corresponding to the uplinktransmission, or a second MAC packet.
 18. The non-transitorycomputer-readable medium of claim 17, wherein the instructions, whenexecuted, cause the wireless device to: transmit the first MAC packetbased on a result of the comparison of the first NDI to the second NDIindicating at least one of: the second NDI and the first NDI having asame value, or a value of the second NDI not being toggled compared to avalue of the first NDI.
 19. The non-transitory computer-readable mediumof claim 17, wherein the instructions, when executed, cause the wirelessdevice to: transmit the second MAC packet based on a result of thecomparison of the first NDI to the second NDI indicating at least oneof: the second NDI and the first NDI not having a same value, or a valueof the second NDI being toggled compared to a value of the first NDI.20. The non-transitory computer-readable medium of claim 17, wherein theinstructions, when executed, cause the wireless device to: store thefirst MAC packet in a buffer associated with a hybrid automatic repeatrequest (HARQ) process indicated by a HARQ identifier.
 21. Thenon-transitory computer-readable medium of claim 17, wherein theinstructions, when executed, cause the wireless device to cancel theuplink transmission by: transmitting, via the uplink radio resource andbased on receiving the first DCI, a first portion of the first MACpacket; and dropping a scheduled transmission, via the uplink radioresource, of a second portion of the first MAC packet.
 22. Thenon-transitory computer-readable medium of claim 17, wherein theinstructions, when executed, cause the wireless device to cancel theuplink transmission by cancelling a transmission associated with thefirst NDI.
 23. The non-transitory computer-readable medium of claim 17,wherein the uplink transmission comprises a physical uplink sharedchannel (PUSCH) transmission.
 24. The non-transitory computer-readablemedium of claim 17, wherein: the first DCI further indicates a hybridautomatic repeat request (HARQ) identifier, and the third DCI indicatesthe HARQ identifier.
 25. A system comprising: a wireless device; and abase station, wherein the wireless device comprises: one or more firstprocessors; and first memory storing first instructions that, whenexecuted by the one or more first processors, cause the wireless deviceto: receive first downlink control information (DCI) that indicates: anuplink radio resource; and a first new data indicator (NDI); receivesecond DCI that indicates that the uplink radio resource is pre-empted;based on detecting that the uplink radio resource is pre-empted, cancelan uplink transmission associated with the uplink radio resource; andbased on cancelling the uplink transmission and based on a comparison ofthe first NDI to a second NDI received via third DCI, transmit one of: afirst media access control (MAC) packet corresponding to the uplinktransmission, or a second MAC packet, and wherein the base stationcomprises: one or more second processors; and second memory storingsecond instructions that, when executed by the one or more secondprocessors, cause the base station to: send the first DCI.
 26. Thesystem of claim 25, wherein the first instructions, when executed by theone or more first processors, cause the wireless device to: transmit thefirst MAC packet based on a result of the comparison of the first NDI tothe second NDI indicating at least one of: the second NDI and the firstNDI having a same value, or a value of the second NDI not being toggledcompared to a value of the first NDI.
 27. The system of claim 25,wherein the first instructions, when executed by the one or more firstprocessors, cause the wireless device to: transmit the second MAC packetbased on a result of the comparison of the first NDI to the second NDIindicating at least one of: the second NDI and the first NDI not havinga same value, or a value of the second NDI being toggled compared to avalue of the first NDI.
 28. The system of claim 25, wherein the firstinstructions, when executed by the one or more first processors, causethe wireless device to: store the first MAC packet in a bufferassociated with a hybrid automatic repeat request (HARQ) processindicated by a HARQ identifier.
 29. The system of claim 25, wherein thefirst instructions, when executed by the one or more first processors,cause the wireless device to cancel the uplink transmission by:transmitting, via the uplink radio resource and based on receiving thefirst DCI, a first portion of the first MAC packet; and dropping ascheduled transmission, via the uplink radio resource, of a secondportion of the first MAC packet.
 30. The system of claim 25, wherein thefirst instructions, when executed by the one or more first processors,cause the wireless device to cancel the uplink transmission bycancelling a transmission associated with the first NDI.
 31. The systemof claim 25, wherein the uplink transmission comprises a physical uplinkshared channel (PUSCH) transmission.
 32. The system of claim 25,wherein: the first DCI further indicates a hybrid automatic repeatrequest (HARQ) identifier, and the third DCI indicates the HARQidentifier.